Triple
T1306976
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Al Nassr FC |
E27900
|
entity |
| Predicate | professionalEra |
P27785
|
FINISHED |
| Object | 21st century |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: 21st century | Statement: [Al Nassr FC, professionalEra, 21st century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: professionalEra Context triple: [Al Nassr FC, professionalEra, 21st century]
-
A.
professionalHead
Indicates that one entity serves as the primary professional leader or chief authority over another entity within an organizational or occupational context.
-
B.
professional
Indicates that one entity has a formal, occupation-related role, service, or expertise in relation to another entity.
-
C.
professionServed
Indicates that an entity has performed work or provided services in a particular profession or occupational role.
-
D.
hasProfessionalStatus
Indicates that an entity holds a particular professional standing, rank, or qualification within a field or occupation.
-
E.
workedAs
Indicates that an entity held a particular job, role, or position, performing work in that capacity.
- F. None of above. chosen
Provenance (4 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69a496d7d83481908f83085854e51328 |
completed | March 1, 2026, 7:43 p.m. |
| NER | Named-entity recognition | batch_69a4c15490a88190872c3d2698a8f9c9 |
completed | March 1, 2026, 10:44 p.m. |
| PD | Predicate disambiguation | batch_69a4bee9e4a88190b22ab2ee831a23c9 |
completed | March 1, 2026, 10:34 p.m. |
| PDg | Predicate description generation | batch_69a4c15361c8819094b8171e780b5560 |
completed | March 1, 2026, 10:44 p.m. |
Created at: March 1, 2026, 7:51 p.m.