Triple
T38406062
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | One-Eyed Willy |
E901330
|
entity |
| Predicate | treasureProtectedBy |
P191153
|
FINISHED |
| Object | elaborate traps |
—
|
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: elaborate traps | Statement: [One-Eyed Willy, treasureProtectedBy, elaborate traps]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: treasureProtectedBy Context triple: [One-Eyed Willy, treasureProtectedBy, elaborate traps]
-
A.
treasureOwnedBy
Indicates that a particular treasure is possessed or legally held by a specific owner.
-
B.
treasureInvolved
Indicates that a situation, event, or action involves or is related to treasure in some significant way.
-
C.
treasureMadeFor
Indicates that a treasure was specifically created, crafted, or designated for a particular recipient, purpose, or context.
-
D.
tressureType
Indicates the specific kind or category of tressure (a heraldic ornamental border around a shield or charge) associated with an entity.
-
E.
heldToProtect
Indicates that one entity is kept in someone’s possession or custody for the purpose of safeguarding or protecting it.
- 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_69f76e61e79c81908b787d83b46ab92b |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fcda3699948190adb57625bae08091 |
completed | May 7, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fd16d08190b0aca6e19a632e99 |
completed | May 7, 2026, 6:25 p.m. |
| PDg | Predicate description generation | batch_69fcda35dc048190a3c90e15230900e0 |
completed | May 7, 2026, 6:30 p.m. |
Created at: May 3, 2026, 4:31 p.m.