Triple
T33719882
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tenderfoot rank |
E863980
|
entity |
| Predicate | onPathTo |
P142543
|
FINISHED |
| Object | Eagle Scout rank |
—
|
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: Eagle Scout rank | Statement: [Tenderfoot rank, onPathTo, Eagle Scout rank]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: onPathTo Context triple: [Tenderfoot rank, onPathTo, Eagle Scout rank]
-
A.
pathTo
chosen
Indicates that one entity serves as a route, way, or means of reaching, accessing, or moving to another entity.
-
B.
ultimatePathTo
Indicates that one entity represents the final, most fundamental, or decisive route, method, or means by which another entity is reached or achieved.
-
C.
locatedOnRouteTo
Indicates that one entity lies along the path or course taken when traveling from a starting point to a specified destination.
-
D.
routeOf
Indicates that one entity is the path, course, or trajectory taken or followed by another entity (such as a vehicle, shipment, or signal).
-
E.
isInDirectionOf
Indicates that one entity is oriented or positioned toward the direction in which another entity lies.
- 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_69f34989871c81908682e22a2fe4b829 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6faeac9288190ac7ce78ea3cdb622 |
completed | May 3, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f6f96dd4c8819093d6a7bd046a9ad5 |
completed | May 3, 2026, 7:29 a.m. |
Created at: May 1, 2026, 1:44 a.m.