Triple
T32760956
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Little Planet |
E837751
|
entity |
| Predicate | conflictLocationFor |
P39379
|
FINISHED |
| Object | Sonic vs Metal Sonic race |
—
|
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: Sonic vs Metal Sonic race | Statement: [Little Planet, conflictLocationFor, Sonic vs Metal Sonic race]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conflictLocationFor Context triple: [Little Planet, conflictLocationFor, Sonic vs Metal Sonic race]
-
A.
conflictLocation
chosen
Indicates the place or geographic area where a conflict, dispute, or confrontation occurs or is centered.
-
B.
conflictSource
Indicates that one entity is the origin, cause, or initiating side of a conflict involving another entity.
-
C.
conflictContext
Indicates the situational background or circumstances within which a conflict between entities occurs or is interpreted.
-
D.
namedForConflict
Indicates that one entity is named after, or in commemoration of, a specific conflict, war, or battle.
-
E.
conflictWith
Indicates that two entities are in opposition or disagreement, such that their goals, actions, or states are incompatible or interfere with 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_69f34939857c8190aa9970c51feec1eb |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f7117e55908190a67105e92bc4830f |
completed | May 3, 2026, 9:12 a.m. |
| PD | Predicate disambiguation | batch_69f70f380690819090cc34763ba460ed |
completed | May 3, 2026, 9:02 a.m. |
Created at: May 1, 2026, 1:13 a.m.