Triple
T25462551
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Simonside dwarfs |
E638088
|
entity |
| Predicate | lure |
P131565
|
FINISHED |
| Object | travelers |
—
|
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: travelers | Statement: [Simonside dwarfs, lure, travelers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lure Context triple: [Simonside dwarfs, lure, travelers]
-
A.
lures
chosen
Indicates that one entity attracts, entices, or draws another entity toward itself, often by offering something appealing or deceptive.
-
B.
trap
Indicates that an entity captures, confines, or ensnares another entity, typically preventing its escape or movement.
-
C.
fishingUse
Indicates that one entity uses another as a tool, method, or context specifically for the activity of fishing.
-
D.
attracts
Indicates that one entity exerts a force or influence that draws another entity toward it.
-
E.
fishedFor
Indicates that one entity attempted to catch another entity (typically an animal or resource) by engaging in fishing activities.
- 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_69e75db8bab08190baca80b4a8c315fd |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f72d0cc08190ba91a9dc39b1d848 |
completed | May 2, 2026, 1:07 p.m. |
| PD | Predicate disambiguation | batch_69f468421ba08190880eac99135e5970 |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 21, 2026, 2:12 p.m.