Triple
T28543899
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Miki Sudo |
E722373
|
entity |
| Predicate | hasRecordIn |
P18283
|
FINISHED |
| Object | hot dog eating |
—
|
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: hot dog eating | Statement: [Miki Sudo, hasRecordIn, hot dog eating]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRecordIn Context triple: [Miki Sudo, hasRecordIn, hot dog eating]
-
A.
containsRecord
Indicates that one entity holds, includes, or stores a particular record within it.
-
B.
hasWrittenRecordsIn
Indicates that an entity has produced or maintains written records in a specified medium, format, or location.
-
C.
hasWorkRecordedThere
Indicates that a person or creator has had their work documented, produced, or otherwise officially recorded at a particular place or institution.
-
D.
hasEntryOn
chosen
Indicates that one entity contains or includes an entry, record, or listing about another entity.
-
E.
isRecord
Indicates that one entity functions as an official or authoritative record of another entity or of some information.
- 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_69f01a5e42348190b1ffbca26e739c84 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69ff5f5ecc808190b2df364da108ff4c |
completed | May 9, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69ff5b84131c8190bf81d7fb53e934bc |
completed | May 9, 2026, 4:06 p.m. |
Created at: April 28, 2026, 3:37 a.m.