Triple
T10742514
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gol Sud |
E253361
|
entity |
| Predicate | relativePositionToPitch |
P47880
|
FINISHED |
| Object | behind one of the goals |
—
|
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: behind one of the goals | Statement: [Gol Sud, relativePositionToPitch, behind one of the goals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relativePositionToPitch Context triple: [Gol Sud, relativePositionToPitch, behind one of the goals]
-
A.
locationRelativeToPitch
chosen
Indicates the spatial position of an entity in relation to the pitch (e.g., above, beside, or within the pitch area).
-
B.
positionRelativeToEarth
Indicates the spatial position or orientation of an entity in relation to the Earth as a reference frame.
-
C.
relativePosition
Indicates the spatial relationship of one entity’s location with respect to another entity’s position.
-
D.
relativePositionInSystem
Indicates the spatial or ordered position an entity occupies within a larger system or structured arrangement.
-
E.
relativePositionOnCourse
Indicates the positional relationship of one participant or object relative to another along a defined course or route.
- 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_69d6aa5e51e8819095f06881cecf152e |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d710456ec88190ad8aff8804d13aa9 |
completed | April 9, 2026, 2:34 a.m. |
| PD | Predicate disambiguation | batch_69d6f30df9948190ab3cdc33977fac14 |
completed | April 9, 2026, 12:30 a.m. |
Created at: April 8, 2026, 9:15 p.m.