Triple
T26697226
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GO TO 2040 comprehensive regional plan |
E673054
|
entity |
| Predicate | isLongRange |
P161128
|
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: [GO TO 2040 comprehensive regional plan, isLongRange, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLongRange Context triple: [GO TO 2040 comprehensive regional plan, isLongRange, true]
-
A.
hasLongerReachThan
Indicates that one entity can extend, influence, or physically reach farther than another entity.
-
B.
isShorterRangeThan
Indicates that one entity has a shorter effective range or distance of operation compared to another entity.
-
C.
hasFiringRange
Indicates that one entity possesses or provides a designated area or capability for discharging weapons over a specified distance.
-
D.
rangeComparedToLongGun
Indicates how the effective range of one weapon compares to that of a long gun (e.g., shorter, equal, or longer range).
-
E.
hasLongFocalLength
Indicates that one entity possesses or is characterized by a focal length that is relatively long compared to a standard or reference.
- 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_69eecda2b49c8190a6c481cfc4c07954 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f6177c7ddc8190b6c96e97be69030d |
completed | May 2, 2026, 3:25 p.m. |
| PD | Predicate disambiguation | batch_69f60b8bb0d08190ab5a9a2a8847c6f4 |
completed | May 2, 2026, 2:34 p.m. |
| PDg | Predicate description generation | batch_69f60f24ed608190bffe6c6084fc2f7a |
completed | May 2, 2026, 2:50 p.m. |
Created at: April 27, 2026, 3:29 a.m.