Triple
T36551696
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bobby |
E901278
|
entity |
| Predicate | hasImaginativeAdventuresWith |
P95848
|
FINISHED |
| Object | Mike |
—
|
NE NERFINISHED |
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: Mike | Statement: [Bobby, hasImaginativeAdventuresWith, Mike]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasImaginativeAdventuresWith Context triple: [Bobby, hasImaginativeAdventuresWith, Mike]
-
A.
hasPerilousAdventure
Indicates that an entity experiences, undertakes, or is involved in a dangerous or high-risk adventure.
-
B.
hasAdventureOn
Indicates that an entity participates in or experiences an adventure that takes place on or during a specified context, such as a time, location, or medium.
-
C.
hasImaginaryFriendCharacter
chosen
Indicates that an entity is associated with or has an imaginary friend character.
-
D.
nonHumanCharacter
Indicates that the character involved in the relation is not a human being (e.g., an animal, creature, AI, or other non-human entity).
-
E.
hasAdventureAt
Indicates that an entity experiences, undertakes, or is involved in an adventure at a specified location or setting.
- 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_69f76e61217081908b79d610fe67b013 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fcab6e888881908ca9e18660928a40 |
completed | May 7, 2026, 3:10 p.m. |
| PD | Predicate disambiguation | batch_69fc4562a5b88190bad48f083a6dcdfa |
completed | May 7, 2026, 7:55 a.m. |
Created at: May 3, 2026, 4:11 p.m.