Triple
T30013709
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Green Monster |
E762536
|
entity |
| Predicate | topSeatingOpened |
P168355
|
FINISHED |
| Object | 2003 |
—
|
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: 2003 | Statement: [Green Monster, topSeatingOpened, 2003]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: topSeatingOpened Context triple: [Green Monster, topSeatingOpened, 2003]
-
A.
seatingPosition
Indicates the relative location or arrangement of an entity’s seat with respect to other seats or a reference point in a seating layout.
-
B.
seatingDirection
Indicates the orientation or facing direction in which an entity is seated relative to a reference point or object.
-
C.
hasSeating
Indicates that one entity provides or contains seating capacity or seating arrangements for another entity.
-
D.
seatLocation
Indicates the spatial position or placement of a seat relative to a reference point or environment.
-
E.
hasRetractableSeating
Indicates that an entity is equipped with seating that can be folded away, collapsed, or otherwise retracted when not in use.
- F. None of above. chosen
Provenance (4 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_69f2246b0c84819094f1250b6a02d277 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6798294288190ae5a5e0a83a20044 |
completed | May 2, 2026, 10:24 p.m. |
| PD | Predicate disambiguation | batch_69f66ec9919881908a187bfc7c4df192 |
completed | May 2, 2026, 9:38 p.m. |
| PDg | Predicate description generation | batch_69f67256d064819094be04fc1bbbc635 |
completed | May 2, 2026, 9:53 p.m. |
Created at: April 29, 2026, 6:45 p.m.