Triple
T34908315
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Theodore Honey |
E1006792
|
entity |
| Predicate | isDoubtedBy |
P59223
|
FINISHED |
| Object | aviation authorities |
—
|
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: aviation authorities | Statement: [Theodore Honey, isDoubtedBy, aviation authorities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isDoubtedBy Context triple: [Theodore Honey, isDoubtedBy, aviation authorities]
-
A.
doubted
chosen
Indicates that one entity questioned the truth, reliability, or likelihood of another entity, action, or claim.
-
B.
debunkedBy
Indicates that a claim, idea, or assertion has been shown to be false or misleading by another party through evidence or argument.
-
C.
believedBy
Indicates that a particular proposition, statement, or entity is held to be true or accepted as real by a specified believer.
-
D.
laterDisputedBy
Indicates that a previously made claim, statement, or assertion is subsequently challenged, questioned, or contradicted by another party.
-
E.
questionedFact
Indicates that one entity has asked about or challenged the truth, accuracy, or validity of a particular fact associated with 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_69f76dc1b4a081909b4c6e4d8ec0aa2d |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f782c98fa08190870b68de2c1ff26a |
completed | May 3, 2026, 5:15 p.m. |
| PD | Predicate disambiguation | batch_69f781020cc4819088c40cb8589504e4 |
completed | May 3, 2026, 5:08 p.m. |
Created at: May 3, 2026, 4 p.m.