Triple
T28325907
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ingraham Direct route |
E717406
|
entity |
| Predicate | sharesApproachWith |
P193298
|
FINISHED |
| Object | Disappointment Cleaver route |
—
|
NE NERFINISHED |
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: Disappointment Cleaver route | Statement: [Ingraham Direct route, sharesApproachWith, Disappointment Cleaver route]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesApproachWith Context triple: [Ingraham Direct route, sharesApproachWith, Disappointment Cleaver route]
-
A.
sharesPracticesWith
Indicates that two entities engage in or follow similar methods, behaviors, or operational practices.
-
B.
sharesValuesWith
Indicates that two entities hold similar or compatible beliefs, principles, or priorities.
-
C.
sharesWith
Indicates that one entity gives another entity access to or use of something it possesses.
-
D.
sharesWorkWith
Indicates that one entity collaborates or participates jointly in work or tasks with another entity.
-
E.
sharesFieldWith
Indicates that two entities are involved in or associated with the same field, discipline, or area of specialization.
- 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_69eff6e6c3b08190ad78de6ba7f04548 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69fd4129a8848190a5002150278ac689 |
completed | May 8, 2026, 1:49 a.m. |
| PD | Predicate disambiguation | batch_69fd3e0515ec8190937c7af71ebc3875 |
completed | May 8, 2026, 1:36 a.m. |
| PDg | Predicate description generation | batch_69fd4128ed908190837ec9936774a1cf |
completed | May 8, 2026, 1:49 a.m. |
Created at: April 28, 2026, 12:28 a.m.