Triple
T35387229
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World 7 |
E1022821
|
entity |
| Predicate | navigationMechanic |
P34226
|
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: [World 7, navigationMechanic, entering and exiting pipes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: navigationMechanic Context triple: [World 7, navigationMechanic, entering and exiting pipes]
-
A.
navigationControlBy
Indicates that one entity directs, manages, or influences the navigation or movement of another entity.
-
B.
navigation
Indicates the act or process of determining and following a path or route from one location or state to another.
-
C.
navigationFunction
Indicates a relationship where one entity serves as a guide or mapping that determines how another entity moves or progresses through a space, system, or state.
-
D.
navigationFrom
Indicates a directional navigation relationship where movement or guidance starts from a specified source location or point.
-
E.
navigationType
chosen
Indicates the method or mode by which movement or traversal is carried out between locations or through an environment.
- 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_69f794f87c548190bfef8c623b5cb165 |
completed | May 3, 2026, 6:33 p.m. |
| PD | Predicate disambiguation | batch_69f7910770108190bdd39ddb5d304f54 |
completed | May 3, 2026, 6:16 p.m. |
Created at: May 3, 2026, 4:03 p.m.