Triple
T16098169
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arnold’s Drive-In |
E390539
|
entity |
| Predicate | ownerCharacter |
P102726
|
FINISHED |
| Object | Arnold Takahashi |
—
|
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: Arnold Takahashi | Statement: [Arnold’s Drive-In, ownerCharacter, Arnold Takahashi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ownerCharacter Context triple: [Arnold’s Drive-In, ownerCharacter, Arnold Takahashi]
-
A.
hasOwnerCharacters
chosen
Indicates that an entity is associated with one or more characters who own or are responsible for it.
-
B.
bossCharacter
Indicates that one character serves as the primary, often more powerful, opponent or leader that others must confront or overcome.
-
C.
character1
Indicates that the subject is identified as the first or primary character in a narrative or context.
-
D.
ownsRightsToCharacter
Indicates that one entity holds the legal rights or ownership over the use and exploitation of a particular character.
-
E.
hasPrimaryCharacter
Indicates that an entity features another entity as its main or central character.
- 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_69d87f198bc48190a8b7e53ca15b7ead |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e1ff6551a48190afb7e0c61e22b541 |
completed | April 17, 2026, 9:37 a.m. |
| PD | Predicate disambiguation | batch_69e182804208819087f35307cd6e4103 |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 4:59 a.m.