Triple
T31224988
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Port Stanley runway |
E796112
|
entity |
| Predicate | locatedInTheatre |
P203372
|
FINISHED |
| Object | South Atlantic Ocean |
—
|
NE NERFINISHED |
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: South Atlantic Ocean | Statement: [Port Stanley runway, locatedInTheatre, South Atlantic Ocean]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInTheatre Context triple: [Port Stanley runway, locatedInTheatre, South Atlantic Ocean]
-
A.
locatedInTheater
Indicates that something is situated within or inside a theater.
-
B.
positionOnTheatre
Indicates the spatial location or placement of something within the layout or seating/area arrangement of a theatre.
-
C.
isPartOfTheater
Indicates that one entity functions as a component, section, or subdivision within a larger theater (such as a theater building, complex, or organizational unit).
-
D.
servedInTheatre
Indicates that an individual performed military or service duties within a specific theater of operations or geographic area during a conflict or campaign.
-
E.
intendedTheatre
Indicates a relationship where an entity is planned, designed, or meant to be performed, shown, or take place in a particular theatre.
- 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_69f224da98f88190ab32f690cce5d303 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a016ebba0448190b5319243e1b2feca |
completed | May 11, 2026, 5:52 a.m. |
| PD | Predicate disambiguation | batch_6a016d2486b4819085efe197ee21b707 |
completed | May 11, 2026, 5:46 a.m. |
| PDg | Predicate description generation | batch_6a016ebace208190af9a6d6d8a31c670 |
completed | May 11, 2026, 5:52 a.m. |
Created at: April 29, 2026, 9:10 p.m.