Triple
T38406076
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | One-Eyed Willy |
E901330
|
entity |
| Predicate | treasureOutcome |
P191423
|
FINISHED |
| Object | partially recovered by the Goonies |
—
|
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: partially recovered by the Goonies | Statement: [One-Eyed Willy, treasureOutcome, partially recovered by the Goonies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: treasureOutcome Context triple: [One-Eyed Willy, treasureOutcome, partially recovered by the Goonies]
-
A.
treasureInvolved
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.
treasureProtectedBy
Indicates that a treasure is guarded, defended, or kept safe by a particular entity or mechanism.
-
E.
tressureType
Indicates the specific kind or category of tressure (a heraldic ornamental border around a shield or charge) associated with an entity.
- 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_69fcdf2394748190b35cead3e208447d |
completed | May 7, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe344ec8190a0471911952f4b82 |
completed | May 7, 2026, 6:37 p.m. |
| PDg | Predicate description generation | batch_69fcdf22ab8881908b257f16522920c5 |
completed | May 7, 2026, 6:51 p.m. |
Created at: May 3, 2026, 4:31 p.m.