Triple
T15600889
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bilröst |
E375028
|
entity |
| Predicate | cannotBeCrossedBy |
P119401
|
FINISHED |
| Object | unworthy beings |
—
|
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: unworthy beings | Statement: [Bilröst, cannotBeCrossedBy, unworthy beings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cannotBeCrossedBy Context triple: [Bilröst, cannotBeCrossedBy, unworthy beings]
-
A.
notCrossing
Indicates that two entities do not intersect, overlap, or pass through each other in space or along their paths.
-
B.
crossedBy
Indicates that one entity (typically a path, line, or boundary) is intersected or traversed by another entity.
-
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.
crossingRequiredFor
Indicates that a particular crossing (such as a bridge, tunnel, or intersection) is necessary to move from one location or path to another.
-
E.
crossingType
Indicates the specific kind or category of crossing (e.g., how or where one thing passes over, through, or across another).
- 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_69d85cce25008190b13b52745fbd719b |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04e621fc4819097e8e85e7ddfdc6c |
completed | April 16, 2026, 2:50 a.m. |
| PD | Predicate disambiguation | batch_69deda844af081909e658ebc9d9b403d |
completed | April 15, 2026, 12:23 a.m. |
| PDg | Predicate description generation | batch_69dff7f05f708190850f1d8782e132b0 |
completed | April 15, 2026, 8:41 p.m. |
Created at: April 10, 2026, 4:12 a.m.