Triple
T18643123
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reference.com |
E455737
|
entity |
| Predicate | supportsNavigationBy |
P103569
|
FINISHED |
| Object | categories |
—
|
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: categories | Statement: [Reference.com, supportsNavigationBy, categories]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsNavigationBy Context triple: [Reference.com, supportsNavigationBy, categories]
-
A.
navigatesUsing
Indicates that one entity moves or travels through an environment by relying on another entity as its means, tool, or method of navigation.
-
B.
navigationSupport
chosen
Indicates that one entity provides assistance, guidance, or tools to help another entity navigate or find its way.
-
C.
hasNavigationUse
Indicates that something is used for navigation or serves a navigational function in relation to another entity.
-
D.
enablesNavigationBetween
Indicates that one entity provides the means or capability for moving or transitioning between two other entities or locations.
-
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_69d8d38ea1e88190997e9b231190ba6f |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5500b6d7c8190b807b772980d913c |
completed | April 19, 2026, 9:58 p.m. |
| PD | Predicate disambiguation | batch_69e478d85864819093cbad5ed9b54878 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:47 a.m.