Triple
T6819191
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Teito Rapid Transit Authority |
E156852
|
entity |
| Predicate | operatedMode |
P26963
|
FINISHED |
| Object | subway |
—
|
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: subway | Statement: [Teito Rapid Transit Authority, operatedMode, subway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatedMode Context triple: [Teito Rapid Transit Authority, operatedMode, subway]
-
A.
operateIn
Indicates that an entity performs its activities, functions, or services within a specified location, context, or domain.
-
B.
operatedAs
Indicates that an entity functioned or was used in the capacity, role, or identity of another entity for some period of time.
-
C.
operatingPattern
chosen
Indicates the characteristic way in which an entity functions or operates over time, such as its typical mode, schedule, or behavioral pattern.
-
D.
operatingStatus
Indicates whether an entity is currently functioning, active, or in service versus inactive, closed, or out of service.
-
E.
operatesOver
Indicates that one entity performs actions or exerts functional control across, upon, or throughout another entity or domain.
- 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_69c688298a288190af3f285d57f76bbe |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d35781e88190a45d1386706d4422 |
completed | March 27, 2026, 6:58 p.m. |
| PD | Predicate disambiguation | batch_69c6d09bb4f881909bf20c188cb3e8e1 |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:17 p.m.