Triple
T26386756
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oklahoma City Streetcar |
E663301
|
entity |
| Predicate | isModernSystem |
P160480
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Oklahoma City Streetcar, isModernSystem, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isModernSystem Context triple: [Oklahoma City Streetcar, isModernSystem, true]
-
A.
isModern
Indicates that something belongs to, reflects, or is characteristic of the contemporary or recent period, especially in style, design, or thinking.
-
B.
hasModernApplication
Indicates that something is currently used or applicable in modern contexts, practices, or technologies.
-
C.
isModernRelativeTo
Indicates that one entity is considered more modern or contemporary in time, style, or development compared to another entity.
-
D.
hasModernPerformance
Indicates that an entity includes, features, or is associated with a contemporary or updated performance or execution of something (such as a work, function, or capability).
-
E.
isModernLine
Indicates that something belongs to, represents, or conforms to a contemporary or current-era style, design, or version within a series or category.
- 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_69ee88374adc81909868f3bab374a32f |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f610bc2b288190ae10e6c27e5df786 |
completed | May 2, 2026, 2:57 p.m. |
| PD | Predicate disambiguation | batch_69f5f800fa9c8190aab0962669fde8ac |
completed | May 2, 2026, 1:11 p.m. |
| PDg | Predicate description generation | batch_69f6018ceb1c8190a6a5f84071659a96 |
completed | May 2, 2026, 1:52 p.m. |
Created at: April 26, 2026, 11:22 p.m.