Triple
T26092947
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cape Luigi |
E658174
|
entity |
| Predicate | hasOriginalCharacterCreator |
P40162
|
FINISHED |
| Object | Nintendo |
—
|
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: Nintendo | Statement: [Cape Luigi, hasOriginalCharacterCreator, Nintendo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOriginalCharacterCreator Context triple: [Cape Luigi, hasOriginalCharacterCreator, Nintendo]
-
A.
hasOriginalCharacter
Indicates that an entity includes, features, or is associated with an original character distinct from pre-existing or canonical characters.
-
B.
hasFounderCharacter
Indicates that an entity has a founder who possesses a specified character trait or set of personal qualities.
-
C.
hasPrimaryCharacter
Indicates that an entity features another entity as its main or central character.
-
D.
creatorOfCharacter
chosen
Indicates that one entity is the originator or author who created or conceived the other entity as a character.
-
E.
creatorNameInOriginalScript
Indicates that the relationship specifies the name of the creator written in the original script or writing system used by that creator.
- 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_69ee5bbfc4d08190a1b206d0ac3a1e8d |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f69edbb7648190bd89c57e0932eac1 |
completed | May 3, 2026, 1:03 a.m. |
| PD | Predicate disambiguation | batch_69f69d17e8d48190b30bcc2f4bd81eb2 |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 26, 2026, 7:48 p.m.