Triple
T23636447
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TRTA |
E583760
|
entity |
| Predicate | operatedMostOf |
P152977
|
FINISHED |
| Object | Tokyo subway network |
—
|
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: Tokyo subway network | Statement: [TRTA, operatedMostOf, Tokyo subway network]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatedMostOf Context triple: [TRTA, operatedMostOf, Tokyo subway network]
-
A.
operatedAmong
Indicates that an entity carried out operations or activities within, or in coordination with, a specified group, set, or collection of other entities.
-
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.
operatedFor
Indicates that one entity performed operations or provided services on behalf of, or in support of, another entity for a certain period or purpose.
-
D.
oftenOperatedBy
Indicates that an entity is frequently or typically operated, controlled, or run by another entity.
-
E.
operatedWith
Indicates that an entity performed an action, function, or process using a specified tool, method, or instrument.
- 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_69e248fe1c2c8190ac914d2442ff3d26 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b1ed03148190a14b3c81ebf7ed99 |
completed | April 29, 2026, 7:23 a.m. |
| PD | Predicate disambiguation | batch_69f118d7903c8190bb590a71771e93af |
completed | April 28, 2026, 8:30 p.m. |
| PDg | Predicate description generation | batch_69f1233300bc8190ac1639bdca1d7d99 |
completed | April 28, 2026, 9:14 p.m. |
Created at: April 17, 2026, 6:47 p.m.