Triple
T36480104
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charlie Andrews |
E898788
|
entity |
| Predicate | firstMeetsHiroIn |
P61227
|
FINISHED |
| Object | Burnt Toast Diner |
E2185882
|
NE 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: Burnt Toast Diner | Statement: [Charlie Andrews, firstMeetsHiroIn, Burnt Toast Diner]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstMeetsHiroIn Context triple: [Charlie Andrews, firstMeetsHiroIn, Burnt Toast Diner]
-
A.
firstMeets
Indicates that one entity encounters or comes into contact with another entity for the first time.
-
B.
firstMeetingPlace
chosen
Indicates the location where two or more entities met each other for the very first time.
-
C.
firstRendezvousMission
Indicates that the mission is the first instance in which two or more entities conduct a rendezvous operation.
-
D.
firstFight
Indicates that the referenced event is the initial instance in which the involved entities engaged in a fight or combat with each other.
-
E.
firstMission
Indicates that an entity is undertaking or associated with its initial mission or assignment in a given context.
- F. None of above.
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_69f76e5a0e088190a2b6706aeb41723c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a39dbc9d784819099246e0d3fbffcee |
completed | June 23, 2026, 1:05 a.m. |
| PD | Predicate disambiguation | batch_6a037a0bf4b88190bdcfae9a14b51f0a |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:10 p.m.