Triple
T31472057
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DDG |
E802885
|
entity |
| Predicate | hasLetterGMeaning |
P192995
|
FINISHED |
| Object | Guided missile |
—
|
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: Guided missile | Statement: [DDG, hasLetterGMeaning, Guided missile]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLetterGMeaning Context triple: [DDG, hasLetterGMeaning, Guided missile]
-
A.
hasLastThreeLettersMeaning
Indicates that the last three letters of one entity (typically a word or string) together form a meaningful unit or have a specific semantic significance.
-
B.
hasLetter
Indicates that one entity contains, includes, or is associated with a specific letter or character.
-
C.
hasLetterName
Indicates that an entity is associated with a specific letter used as its name or designation.
-
D.
hasLetterBy
Indicates that an entity possesses or is associated with a letter authored or sent by another entity.
-
E.
hasLettersFor
Indicates that one entity possesses or contains written correspondence intended for another entity.
- 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_69f348c84c1c81908739f100ecf7394e |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fd35d108908190b79b1e8e6bbd62aa |
completed | May 8, 2026, 1:01 a.m. |
| PD | Predicate disambiguation | batch_69fd34cb46108190b43c3b7f67ec4cd4 |
completed | May 8, 2026, 12:56 a.m. |
| PDg | Predicate description generation | batch_69fd35d029588190a525aa8a506e7708 |
completed | May 8, 2026, 1:01 a.m. |
Created at: April 30, 2026, 9:26 p.m.