Triple
T26032697
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Propeller Luigi |
E647475
|
entity |
| Predicate | hasSiblingCounterpart |
P6587
|
FINISHED |
| Object | Propeller Mario |
—
|
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: Propeller Mario | Statement: [Propeller Luigi, hasSiblingCounterpart, Propeller Mario]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSiblingCounterpart Context triple: [Propeller Luigi, hasSiblingCounterpart, Propeller Mario]
-
A.
hasSmallerCounterpart
Indicates that one entity has another entity as its corresponding version that is smaller in size, scale, or magnitude.
-
B.
hasCounterpart
chosen
Indicates that one entity corresponds to, matches, or serves as an equivalent or parallel version of another entity.
-
C.
hasCounterpartName
Indicates that an entity has an alternative or corresponding name used as its counterpart in another context, system, or representation.
-
D.
isTwinWith
Indicates that two entities are twins, sharing the same birth parents and being born at (or very near) the same time.
-
E.
hasSiblingExchange
Indicates a reciprocal relationship in which two entities are siblings of each other.
- 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_69e77e8b60e88190a3b26c4f0032a2c2 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f65aa07c048190a5df30d53d8f0cf5 |
completed | May 2, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69f659cc571c819097e51e531961d812 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 22, 2026, 9:06 a.m.