Triple
T27254564
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LongRanger |
E687575
|
entity |
| Predicate | notableVariantOf |
P154137
|
FINISHED |
| Object | Bell 206 JetRanger |
—
|
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: Bell 206 JetRanger | Statement: [LongRanger, notableVariantOf, Bell 206 JetRanger]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableVariantOf Context triple: [LongRanger, notableVariantOf, Bell 206 JetRanger]
-
A.
notableVariation
Indicates that one entity represents a significant or noteworthy deviation or difference from another entity within a given context.
-
B.
notableMemberVariant
Indicates that an entity is a specific variant or version of a notable member within a group, class, or category.
-
C.
denotesVariantOf
chosen
Indicates that one entity is a variant or alternative form of another, typically sharing core identity or function with some differences.
-
D.
likelyVariantOf
Indicates that one entity is probably a variant, version, or alternative form of another entity, based on available evidence or similarity.
-
E.
famousVariant
Indicates that one entity is a well-known or widely recognized version or form of 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_69ef35567e808190a94458cd44ebff0c |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69ffb1218cb08190a814c7f0833501a7 |
completed | May 9, 2026, 10:11 p.m. |
| PD | Predicate disambiguation | batch_69ffb083d6988190b2757e0cfd629b75 |
completed | May 9, 2026, 10:09 p.m. |
Created at: April 27, 2026, 10:48 a.m.