Triple
T33009180
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Legacy 650 |
E844592
|
entity |
| Predicate | hasExtendedRangeComparedTo |
P21058
|
FINISHED |
| Object | Legacy 600 |
—
|
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: Legacy 600 | Statement: [Legacy 650, hasExtendedRangeComparedTo, Legacy 600]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasExtendedRangeComparedTo Context triple: [Legacy 650, hasExtendedRangeComparedTo, Legacy 600]
-
A.
hasLongerReachThan
chosen
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.
isLongRange
Indicates that the relationship or action involves operating effectively over a large or extended distance.
-
D.
isExtendedVersionOf
Indicates that one entity is a longer or more developed form of another, typically adding content or features while preserving the original’s core.
-
E.
isMoreRemoteThan
Indicates that one entity is located at a greater distance or in a more out-of-the-way location compared to another entity.
- 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_69f3494e59f08190b9127c693e5c7e8f |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fbad1e94988190b86d447a68e65067 |
completed | May 6, 2026, 9:05 p.m. |
| PD | Predicate disambiguation | batch_69fba881b8e0819094790935152b99a1 |
completed | May 6, 2026, 8:45 p.m. |
Created at: May 1, 2026, 1:23 a.m.