Triple
T28892447
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amos Boone |
E732736
|
entity |
| Predicate | hasQuestType |
P137500
|
FINISHED |
| Object | rescue quest |
—
|
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: rescue quest | Statement: [Amos Boone, hasQuestType, rescue quest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasQuestType Context triple: [Amos Boone, hasQuestType, rescue quest]
-
A.
questType
chosen
Indicates the specific category or nature of a quest that characterizes what kind of mission or objective it represents.
-
B.
hasMissionIn
Indicates that an entity carries out, undertakes, or is assigned a mission within a specified location or region.
-
C.
hasAchievementType
Indicates that an achievement is classified under a specific type or category of achievement.
-
D.
hasMissionTo
Indicates that an entity is assigned or dedicated to carrying out a specific mission, task, or purpose related to another entity or objective.
-
E.
hasMissionActivity
Indicates that an entity is associated with, performs, or is involved in a specific mission-related activity.
- 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_69f05b08c2008190ac426a035a2ed66d |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f6691f5e188190b12c7b2eb729a45e |
completed | May 2, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69f6659b62fc8190b21555d0ba54db2d |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 7:56 a.m.