Triple
T25201354
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Samuel Drake |
E631132
|
entity |
| Predicate | associatedTreasure |
P148703
|
FINISHED |
| Object | Henry Avery's pirate treasure |
—
|
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: Henry Avery's pirate treasure | Statement: [Samuel Drake, associatedTreasure, Henry Avery's pirate treasure]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedTreasure Context triple: [Samuel Drake, associatedTreasure, Henry Avery's pirate treasure]
-
A.
treasureInvolved
chosen
Indicates that a situation, event, or action involves or is related to treasure in some significant way.
-
B.
treasureOwnedBy
Indicates that a particular treasure is possessed or legally held by a specific owner.
-
C.
treasureMadeFor
Indicates that a treasure was specifically created, crafted, or designated for a particular recipient, purpose, or context.
-
D.
associatedFinds
Indicates that one entity is linked to or connected with another entity through related findings, results, or discovered information.
-
E.
notableRelic
Indicates that an entity is a historically or culturally significant relic associated with another entity (such as a place, person, or event).
- 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_69e75a8b86c4819089eda22c843b739f |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f7886be6d8819095ec62e4f2cee858 |
completed | May 3, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69f7841440f48190b4346c08855951d2 |
completed | May 3, 2026, 5:21 p.m. |
Created at: April 21, 2026, 12:51 p.m.