Triple
T33408226
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chagu Chagu Umakko |
E855496
|
entity |
| Predicate | distanceOfProcession |
P156945
|
FINISHED |
| Object | approximately 13 kilometers |
—
|
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: approximately 13 kilometers | Statement: [Chagu Chagu Umakko, distanceOfProcession, approximately 13 kilometers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceOfProcession Context triple: [Chagu Chagu Umakko, distanceOfProcession, approximately 13 kilometers]
-
A.
numberOfDistances
Indicates the count of distinct distance values associated with or measured between entities in a given context.
-
B.
hopDistance
Indicates the number of intermediate steps or "hops" required to traverse from one entity to another within a network or graph.
-
C.
distanceFromPredecessor
Indicates the measured distance separating an entity from the one that immediately precedes it in a sequence or ordering.
-
D.
distanceToTerminal
Indicates the measured or calculated distance from a given entity or location to a specified terminal point or facility.
-
E.
pathLength
chosen
Indicates the measured distance or length of a path connecting two points or locations.
- 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_69f3496f04a08190804e56ac5098b8e4 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379f505c88190ac0879ab422c3054 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:36 a.m.