Triple
T34117696
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Andrew Morris |
E875017
|
entity |
| Predicate | helpsHimNavigate |
P178683
|
FINISHED |
| Object | friendship |
—
|
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: friendship | Statement: [Andrew Morris, helpsHimNavigate, friendship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: helpsHimNavigate Context triple: [Andrew Morris, helpsHimNavigate, friendship]
-
A.
navigationProblemAddressed
Indicates that a navigation-related issue, obstacle, or challenge has been identified and dealt with or resolved.
-
B.
usedToNavigate
Indicates that one entity served as a means or tool for another entity to find or follow a route or direction.
-
C.
navigation
Indicates the act or process of determining and following a path or route from one location or state to another.
-
D.
navigatesUsing
Indicates that one entity moves or travels through an environment by relying on another entity as its means, tool, or method of navigation.
-
E.
navigationalFunction
Indicates a relationship where something serves to guide, direct, or assist movement or orientation within a space or system.
- 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_69f349a9271c81909576994c9ef7b179 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f713bfdc148190a249a7874320bab8 |
completed | May 3, 2026, 9:22 a.m. |
| PD | Predicate disambiguation | batch_69f7127884388190884f23d181a65d19 |
completed | May 3, 2026, 9:16 a.m. |
| PDg | Predicate description generation | batch_69f7135fa2988190a20a94cfe616d754 |
completed | May 3, 2026, 9:20 a.m. |
Created at: May 1, 2026, 1:53 a.m.