Triple
T27543601
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EAFF |
E695300
|
entity |
| Predicate | worksWithinStructureOf |
P112267
|
FINISHED |
| Object | Asian football structure |
—
|
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: Asian football structure | Statement: [EAFF, worksWithinStructureOf, Asian football structure]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: worksWithinStructureOf Context triple: [EAFF, worksWithinStructureOf, Asian football structure]
-
A.
partOfWorkStructure
Indicates that one work-related component, role, or task is included within or belongs to a larger organizational or work structure.
-
B.
refersToWorkStructure
Indicates that one entity references or is associated with a particular work-related organizational structure or framework.
-
C.
workStructure
Indicates how work is organized, arranged, or structured within or between entities.
-
D.
structurePartOf
Indicates that one structure is a constituent or component of a larger, encompassing structure.
-
E.
worksWithinSystem
chosen
Indicates that an entity performs its functions or activities while operating inside a specified system, framework, or organizational structure.
- F. None of above.
Provenance (3 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_69ef5386c3e08190bfe33aa326e1f72b |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f68805b4848190b75da14996d52a38 |
completed | May 2, 2026, 11:25 p.m. |
| PD | Predicate disambiguation | batch_69f68609c0b08190a8e1238a4d97c270 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 27, 2026, 1:32 p.m.