Triple
T17701058
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tal’s Hill |
E441300
|
entity |
| Predicate | positionRelativeToField |
P42535
|
FINISHED |
| Object | center field |
—
|
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: center field | Statement: [Tal’s Hill, positionRelativeToField, center field]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionRelativeToField Context triple: [Tal’s Hill, positionRelativeToField, center field]
-
A.
positionInField
Indicates the specific role, location, or functional placement an entity occupies within a defined field, domain, or area of activity.
-
B.
positionInFrame
Indicates the spatial location or coordinates of an entity within a specific frame or reference image.
-
C.
positionedRelativeTo
chosen
Indicates that one entity’s spatial location is defined or described in relation to the position of another entity.
-
D.
relativePositionInSystem
Indicates the spatial or ordered position an entity occupies within a larger system or structured arrangement.
-
E.
relativePosition
Indicates the spatial relationship of one entity’s location with respect to another entity’s position.
- 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_69d8b9ea20b48190ace88bb46b01e6a9 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e4715ae1fc81908438a1bba970c6ec |
completed | April 19, 2026, 6:08 a.m. |
| PD | Predicate disambiguation | batch_69e3cde601d4819097903f471f1fe99a |
completed | April 18, 2026, 6:31 p.m. |
Created at: April 10, 2026, 10:04 a.m.