Triple
T7120164
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Park Street metro station |
E165927
|
entity |
| Predicate | hasCommercialImportance |
P74963
|
FINISHED |
| Object | high |
—
|
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: high | Statement: [Park Street metro station, hasCommercialImportance, high]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCommercialImportance Context triple: [Park Street metro station, hasCommercialImportance, high]
-
A.
hasEconomicImportanceFor
Indicates that one entity holds economic value, benefit, or significance for another entity.
-
B.
hasIndustrialSignificance
Indicates that something plays an important role or has notable impact within industrial processes, production, or applications.
-
C.
isImportantFor
Indicates that something holds significant value, relevance, or necessity in relation to something else.
-
D.
hasNationalImportance
Indicates that something possesses significance or relevance at the level of an entire nation, rather than just local or regional importance.
-
E.
hasCommercialFunction
Indicates that an entity serves a commercial role or purpose, such as engaging in trade, sales, or other profit-oriented activities.
- 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_69c6888227bc8190a1394679e3116f90 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e61ca6a88190a0eb9f287e3b723c |
completed | March 27, 2026, 8:18 p.m. |
| PD | Predicate disambiguation | batch_69c6e1c7289881909f3b533c384f9ed4 |
completed | March 27, 2026, 8 p.m. |
| PDg | Predicate description generation | batch_69c6e4a15b088190bee9a23e94aaac53 |
completed | March 27, 2026, 8:12 p.m. |
Created at: March 27, 2026, 2:43 p.m.