Triple
T35639075
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NWX |
E1029806
|
entity |
| Predicate | openedAsCodeFor |
P3746
|
FINISHED |
| Object | New Cross railway station |
—
|
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: New Cross railway station | Statement: [NWX, openedAsCodeFor, New Cross railway station]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedAsCodeFor Context triple: [NWX, openedAsCodeFor, New Cross railway station]
-
A.
openedAs
Indicates that one entity began operating, functioning, or being available to the public under the form, name, or role of another entity.
-
B.
openedAsComplex
Indicates that one entity was inaugurated or began operation specifically as a multi-part or multi-use complex, rather than as a single standalone facility.
-
C.
codeFor
chosen
Indicates that one entity serves as the implementation, encoding, or programmatic representation for another entity.
-
D.
openedAsNumber
Indicates that one entity initiated or accessed another entity in a manner represented or tracked by a numeric value (such as a count or identifier).
-
E.
openedWith
Indicates that an entity is opened, initiated, or accessed using a specified tool, method, or instrument.
- 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_69f76e087bdc8190a4794bf9c0bd7634 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd76d1e5208190a6f26651492d1e3c |
completed | May 8, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69fd702a226c81908edfda00f4be4130 |
completed | May 8, 2026, 5:10 a.m. |
Created at: May 3, 2026, 4:05 p.m.