Triple
T36554885
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Helcaraxë |
E901675
|
entity |
| Predicate | notTraversedBy |
P100661
|
FINISHED |
| Object | Fëanor's host |
—
|
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: Fëanor's host | Statement: [Helcaraxë, notTraversedBy, Fëanor's host]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notTraversedBy Context triple: [Helcaraxë, notTraversedBy, Fëanor's host]
-
A.
notVisitedBy
Indicates that a particular entity has not been visited or accessed by another specified entity.
-
B.
notCrossing
chosen
Indicates that two entities do not intersect, overlap, or pass through each other in space or along their paths.
-
C.
notTransmittedBy
Indicates that a particular entity does not serve as a carrier or medium through which something (such as a disease, signal, or information) is passed from one entity to another.
-
D.
partlyTraversedBy
Indicates that one entity is crossed or passed through by another entity, but only along a portion of its extent rather than its full length or area.
-
E.
notOnTrackOf
Indicates that an entity is not progressing according to the expected or planned course, schedule, or objective associated with another 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_69f76e634e9481908c9ba1b87ab87c26 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c371931c8190afb1d4dd5157f92c |
completed | May 3, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69f7c1baf25c8190a78dd54a400d2c50 |
completed | May 3, 2026, 9:44 p.m. |
Created at: May 3, 2026, 4:11 p.m.