Triple
T13812632
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pro D2 |
E331930
|
entity |
| Predicate | sitsBelow |
P24809
|
FINISHED |
| Object | Top 14 |
—
|
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: Top 14 | Statement: [Pro D2, sitsBelow, Top 14]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sitsBelow Context triple: [Pro D2, sitsBelow, Top 14]
-
A.
sitsAbove
Indicates that one entity is positioned directly higher than and vertically over another entity.
-
B.
liesBelow
chosen
Indicates that one entity is positioned at a lower vertical level than another entity.
-
C.
existsBelow
Indicates that at least one instance of an entity is located or occurs at a lower level or position relative to another entity.
-
D.
occursBelow
Indicates that one event or object takes place or is positioned at a lower level or beneath another in a spatial or hierarchical sense.
-
E.
canBePlacedUnder
Indicates that one entity is allowed or able to be positioned beneath another entity in a spatial or structural arrangement.
- 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_69d81c59f8808190a851bc56afdc55e9 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de027198f8819095da3e714ac241f5 |
completed | April 14, 2026, 9:01 a.m. |
| PD | Predicate disambiguation | batch_69dbc862e9608190bd8a3d883959b7e4 |
completed | April 12, 2026, 4:29 p.m. |
Created at: April 9, 2026, 10:12 p.m.