Triple
T22267582
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hoderi |
E550388
|
entity |
| Predicate | keyItemInMyth |
P7606
|
FINISHED |
| Object | fishing hook |
—
|
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: fishing hook | Statement: [Hoderi, keyItemInMyth, fishing hook]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keyItemInMyth Context triple: [Hoderi, keyItemInMyth, fishing hook]
-
A.
keyMiracle
Indicates that an event or action is regarded as a central or decisive miracle within a given context or narrative.
-
B.
keyComponent
Indicates that one entity is an essential or foundational part required for the proper function, structure, or identity of another entity.
-
C.
keyFortress
Indicates that one entity functions as a key or means of access, control, or unlocking for a particular fortress or strongly secured place represented by the other entity.
-
D.
key
chosen
Indicates that one entity functions as a key (literal or metaphorical) that unlocks, enables access to, or provides a crucial solution or control over another entity.
-
E.
keySector
Indicates that an entity operates in, belongs to, or is primarily associated with a particularly important or strategic sector within a broader domain or economy.
- 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_69e11e43d8208190aff4f9cf7f2c2a8a |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f141bd0ea88190b3574883b695d56c |
completed | April 28, 2026, 11:24 p.m. |
| PD | Predicate disambiguation | batch_69e72ff0363081909f794d19c8a64837 |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:39 p.m.