Triple
T32378011
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DataRelation |
E827339
|
entity |
| Predicate | supportsNavigationFrom |
P31671
|
FINISHED |
| Object | parent row to child rows |
—
|
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: parent row to child rows | Statement: [DataRelation, supportsNavigationFrom, parent row to child rows]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsNavigationFrom Context triple: [DataRelation, supportsNavigationFrom, parent row to child rows]
-
A.
navigationSupport
Indicates that one entity provides assistance, guidance, or tools to help another entity navigate or find its way.
-
B.
enablesNavigationBetween
Indicates that one entity provides the means or capability for moving or transitioning between two other entities or locations.
-
C.
navigableFrom
chosen
Indicates that one location or entity can be reached or traversed from another, typically via a valid path, route, or connection.
-
D.
hasNavigationUse
Indicates that something is used for navigation or serves a navigational function in relation to another entity.
-
E.
isNavigableVia
Indicates that one entity can be reached, traversed, or accessed by means of another entity (such as a route, medium, or pathway).
- 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_69f349177ddc8190ab0583f05597056b |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379edf2d88190b492fca86ed23cac |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 12:51 a.m.