Triple
T1269172
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Injun Joe |
E15669
|
entity |
| Predicate | hides |
P5597
|
FINISHED |
| Object | treasure in the cave |
—
|
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: treasure in the cave | Statement: [Injun Joe, hides, treasure in the cave]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hides Context triple: [Injun Joe, hides, treasure in the cave]
-
A.
hidesFrom
Indicates that one entity actively avoids being seen, detected, or encountered by another entity.
-
B.
coverUpBy
Indicates that one entity conceals, suppresses, or hides the actions, information, or wrongdoing associated with another entity.
-
C.
obscuredIn
Indicates that one entity is hidden, blocked, or made less visible due to the presence or influence of another entity.
-
D.
covered
chosen
Indicates that one entity lies over or on top of another entity so as to conceal, protect, or obscure it.
-
E.
disguisedAs
Indicates that one entity is intentionally presenting itself as, or made to appear as, another entity in order to conceal its true identity.
- 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_69a4935a94308190bb92555b79032824 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4c03aaa8c8190bacb7de5a38329da |
completed | March 1, 2026, 10:39 p.m. |
| PD | Predicate disambiguation | batch_69a4bede52a081909665d60acbe41d31 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:50 p.m.