Triple
T15393876
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dromi |
E368118
|
entity |
| Predicate | bound |
P98255
|
FINISHED |
| Object | Fenrir temporarily |
—
|
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: Fenrir temporarily | Statement: [Dromi, bound, Fenrir temporarily]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bound Context triple: [Dromi, bound, Fenrir temporarily]
-
A.
binding
Indicates that one entity physically or chemically attaches, adheres, or forms a stable association with another entity.
-
B.
boundFor
Indicates that something is destined, directed, or scheduled to go toward a particular destination or target.
-
C.
boundEntity
chosen
Indicates that one entity is constrained, tied, or otherwise held in a fixed relationship or dependency to another entity.
-
D.
oftenBoundIn
Indicates that one entity is frequently enclosed, packaged, or contained within another entity.
-
E.
held
Indicates that one entity physically grasped, carried, or kept another entity in its possession or control.
- 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_69d85a1551a08190ba2caea7cd51c639 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e7838b48190862b43c6c8620692 |
completed | April 16, 2026, 1:42 a.m. |
| PD | Predicate disambiguation | batch_69ded27b8cac8190bfa77698d53c5d1c |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:19 a.m.