Triple
T1448618
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Universal City/Studio City station |
E31233
|
entity |
| Predicate | hasSubwayService |
P10156
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Universal City/Studio City station, hasSubwayService, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSubwayService Context triple: [Universal City/Studio City station, hasSubwayService, yes]
-
A.
subwayServices
chosen
Indicates that one entity provides or operates subway transportation services for another entity or area.
-
B.
hasMetroLine
Indicates that a location or area is served by, or connected to, a specific metro (subway) line.
-
C.
subwayLine
Indicates that there is a subway line connection or service relationship between the referenced entities.
-
D.
hasShuttleLine
Indicates that there is a shuttle service or route operating between the related entities.
-
E.
hasUndergroundSection
Indicates that an entity includes a portion or segment that is located below ground level.
- 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_69a499171a28819085b993a3ac78e363 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c55c408c8190917ed44d9070a2fb |
completed | March 1, 2026, 11:01 p.m. |
| PD | Predicate disambiguation | batch_69a4c47a840c819083307a65c027a19e |
completed | March 1, 2026, 10:58 p.m. |
Created at: March 1, 2026, 8 p.m.