Triple
T34640669
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Taur-e-Ndaedelos |
E889544
|
entity |
| Predicate | crossedByCharacters |
P416
|
FINISHED |
| Object | Bilbo 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: Bilbo Baggins | Statement: [Taur-e-Ndaedelos, crossedByCharacters, Bilbo Baggins]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crossedByCharacters Context triple: [Taur-e-Ndaedelos, crossedByCharacters, Bilbo Baggins]
-
A.
crossedBy
chosen
Indicates that one entity (typically a path, line, or boundary) is intersected or traversed by another entity.
-
B.
followsCharactersAcross
Indicates that one entity persistently tracks or accompanies specific characters as they move or act across different scenes, locations, or contexts.
-
C.
crossingOf
Indicates that one entity serves as the intersection or crossing point of two or more linear features, such as roads, paths, or tracks.
-
D.
crossedWith
Indicates that one entity has moved from one side of another entity or boundary to the opposite side, typically by passing over or through it.
-
E.
crossErectedBy
Indicates that a particular cross was constructed, installed, or set up by a specified agent or entity.
- 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_69f349d724848190b63ad3407e0006d9 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fb6fdc7eb081908ab8475efb38c430 |
completed | May 6, 2026, 4:44 p.m. |
| PD | Predicate disambiguation | batch_69fb5a986e588190b7a10892bd2ff44c |
completed | May 6, 2026, 3:13 p.m. |
Created at: May 1, 2026, 2:04 a.m.