Triple
T35387197
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pipe Maze |
E1022820
|
entity |
| Predicate | hasTraversalMethod |
P192604
|
FINISHED |
| Object | entering and exiting pipes |
—
|
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: entering and exiting pipes | Statement: [Pipe Maze, hasTraversalMethod, entering and exiting pipes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTraversalMethod Context triple: [Pipe Maze, hasTraversalMethod, entering and exiting pipes]
-
A.
hasTraverse
Indicates that one entity moves through, across, or along the extent of another entity or space.
-
B.
usesTraversal
chosen
Indicates that one entity performs or relies on a traversal process or path to interact with, reach, or operate on another entity.
-
C.
hasEdgeTraversal
Indicates that one entity moves along, crosses, or otherwise traverses an edge or connection between nodes in a graph or network.
-
D.
enablesTraversal
Indicates that one entity provides the means or capability for another entity to move through, across, or along something.
-
E.
hasTrailDestination
Indicates that a trail leads to or ends at a particular destination.
- 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_69f76df34ba48190bd80f0814cdcd540 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ffb1218cb08190a814c7f0833501a7 |
completed | May 9, 2026, 10:11 p.m. |
| PD | Predicate disambiguation | batch_69ffb083d6988190b2757e0cfd629b75 |
completed | May 9, 2026, 10:09 p.m. |
Created at: May 3, 2026, 4:03 p.m.