Triple
T2012048
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Open Championship |
E43708
|
entity |
| Predicate | typicalFieldSize |
P7759
|
FINISHED |
| Object | 156 players |
—
|
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: 156 players | Statement: [The Open Championship, typicalFieldSize, 156 players]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalFieldSize Context triple: [The Open Championship, typicalFieldSize, 156 players]
-
A.
fieldSize
chosen
Indicates the magnitude or dimensions of a field associated with an entity or context.
-
B.
typicalFields
Indicates the standard or commonly occurring attributes or data fields that are usually associated with an entity or record.
-
C.
typicalWidth
Indicates the usual or characteristic width associated with an entity, as opposed to an exact or measured width in a specific instance.
-
D.
typicalUnitSize
Indicates the standard or most common size or quantity in which something is typically measured, packaged, or used.
-
E.
typicalLength
Indicates the usual or characteristic length associated with an entity or phenomenon.
- 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_69a88716e9f08190946313fdc949e3cf |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb8b2ed6c8190ad51f0af90db2a02 |
completed | March 7, 2026, 5:33 a.m. |
| PD | Predicate disambiguation | batch_69abb7a03a1c81909ad50d56667db2d5 |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:37 p.m.