Triple
T36615880
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Redhorn Pass |
E903601
|
entity |
| Predicate | attemptedCrossingBy |
P186076
|
FINISHED |
| Object | Frodo Baggins |
—
|
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: Frodo Baggins | Statement: [Redhorn Pass, attemptedCrossingBy, Frodo Baggins]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: attemptedCrossingBy Context triple: [Redhorn Pass, attemptedCrossingBy, Frodo Baggins]
-
A.
crossingOf
Indicates that one entity serves as the intersection or crossing point of two or more linear features, such as roads, paths, or tracks.
-
B.
crossedBy
Indicates that one entity (typically a path, line, or boundary) is intersected or traversed by another entity.
-
C.
crossingOpened
Indicates that a crossing (such as a road, rail, or pedestrian crossing) has been opened or made available for passage.
-
D.
crossedFrom
Indicates that an entity moved across a boundary or dividing line starting from a specified origin location or side.
-
E.
createdByCrossing
Indicates that something was produced as a result of crossing or hybridizing two or more distinct entities.
- 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_69f76e6960e4819092047756ceb9a17e |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c83f5960819089610ed39c839678 |
completed | May 3, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69f7c477a4d481908f52e55b6688f60c |
completed | May 3, 2026, 9:56 p.m. |
| PDg | Predicate description generation | batch_69f7c776b4088190bef550c869da530d |
completed | May 3, 2026, 10:08 p.m. |
Created at: May 3, 2026, 4:11 p.m.