Triple
T17133499
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diros Caves |
E415777
|
entity |
| Predicate | exploredLength |
P126230
|
FINISHED |
| Object | several 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: several kilometers | Statement: [Diros Caves, exploredLength, several kilometers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exploredLength Context triple: [Diros Caves, exploredLength, several kilometers]
-
A.
exploredWith
Indicates that one entity explored something together with another entity as companions or partners in the exploration.
-
B.
exploredDuring
Indicates that an entity was explored or investigated within the time frame or context of a specified event or period.
-
C.
explored
Indicates that an entity has traveled through, examined, or investigated another entity or area, typically to discover or learn more about it.
-
D.
exploresFor
Indicates that one entity actively investigates or searches within or on behalf of another entity, typically to discover or obtain something for that other entity’s benefit.
-
E.
willBeExploredBy
Indicates that something is expected or planned to be examined, investigated, or studied by a particular agent in the future.
- 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_69d886d15af4819092f92f8a129763e6 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3f02cbb7881908aa69c3443d149d5 |
completed | April 18, 2026, 8:57 p.m. |
| PD | Predicate disambiguation | batch_69e3830192ac819091344a9e5a36c8c9 |
completed | April 18, 2026, 1:11 p.m. |
| PDg | Predicate description generation | batch_69e3873f62108190966c4e741ebd548d |
completed | April 18, 2026, 1:29 p.m. |
Created at: April 10, 2026, 5:36 a.m.