Triple
T5495694
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Devil's Throat |
E144204
|
entity |
| Predicate | hasSprayReach |
P45893
|
FINISHED |
| Object | visible from distance |
—
|
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: visible from distance | Statement: [Devil's Throat, hasSprayReach, visible from distance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSprayReach Context triple: [Devil's Throat, hasSprayReach, visible from distance]
-
A.
hasSpray
Indicates that one entity possesses, contains, or is equipped with a spray or spraying capability in relation to another entity or context.
-
B.
hasLongerReachThan
Indicates that one entity can extend, influence, or physically reach farther than another entity.
-
C.
tieneAlcance
chosen
Indicates that something possesses or has a certain scope, reach, or range of effect in relation to something else.
-
D.
hasRefuellingCapabilityFor
Indicates that one entity is capable of providing or performing refuelling operations for another entity.
-
E.
hasSpice
Indicates that one entity contains, includes, or is characterized by a particular spice or set of spices.
- 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_69c008f5a2748190bce7a39aabf87a6d |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c01f08c2a4819093e772a1497c7ecc |
completed | March 22, 2026, 4:55 p.m. |
| PD | Predicate disambiguation | batch_69c01b052f3c81909f71c6add0f35a6f |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:32 p.m.