Triple
T25655869
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mahasankatey Shonku |
E643233
|
entity |
| Predicate | hasPerilousAdventure |
P168894
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Mahasankatey Shonku, hasPerilousAdventure, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPerilousAdventure Context triple: [Mahasankatey Shonku, hasPerilousAdventure, yes]
-
A.
hasMisadventures
Indicates that an entity experiences or is involved in a series of troublesome, chaotic, or comically unfortunate events.
-
B.
hasAdventureAt
Indicates that an entity experiences, undertakes, or is involved in an adventure at a specified location or setting.
-
C.
hasSoloAdventure
Indicates that an entity participates in or is associated with an adventure undertaken alone, without companions.
-
D.
madeExpeditionsTo
Indicates that an entity undertook one or more exploratory or travel expeditions to a specified destination or location.
-
E.
hasNotableExpedition
Indicates that an entity is associated with a significant or noteworthy expedition, journey, or exploratory mission.
- 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_69e77e7d8a848190a98d0162325fd780 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f67866e9248190b7ba218f9ca2ae8d |
completed | May 2, 2026, 10:19 p.m. |
| PD | Predicate disambiguation | batch_69f675fd59608190b246383435e68fce |
completed | May 2, 2026, 10:09 p.m. |
| PDg | Predicate description generation | batch_69f676c35f3481909b9ba18a5662d6ce |
completed | May 2, 2026, 10:12 p.m. |
Created at: April 21, 2026, 6:32 p.m.