Triple
T1675721
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tehran Bus Rapid Transit |
E36226
|
entity |
| Predicate | hasHighFrequency |
P26668
|
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: [Tehran Bus Rapid Transit, hasHighFrequency, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHighFrequency Context triple: [Tehran Bus Rapid Transit, hasHighFrequency, true]
-
A.
hasHigh
Indicates that an entity possesses a high level, degree, or intensity of a specified attribute or property.
-
B.
hasHighPropertyValues
Indicates that the associated entity possesses property values that are above a defined or typical threshold.
-
C.
isFrequently
chosen
Indicates that an action, state, or relationship occurs often or with high regularity between the related entities.
-
D.
usesFrequency
Indicates that one entity employs or operates another entity at a specified rate, interval, or number of occurrences over time.
-
E.
hasHighProfileOwnership
Indicates that an entity is owned, controlled, or significantly invested in by a prominent or high-profile individual or organization.
- 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_69a886139ed081909af0940aa9313512 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69ab272a653481908f48aa1eed5de8a4 |
completed | March 6, 2026, 7:12 p.m. |
| PD | Predicate disambiguation | batch_69aa61b2f6288190b2348ef7d7e4672d |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:29 p.m.