Triple
T6067108
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Solar Opposites |
E135186
|
entity |
| Predicate | originOfProtagonists |
P28569
|
FINISHED |
| Object | planet Shlorp |
—
|
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: planet Shlorp | Statement: [Solar Opposites, originOfProtagonists, planet Shlorp]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originOfProtagonists Context triple: [Solar Opposites, originOfProtagonists, planet Shlorp]
-
A.
protagonistOrigin
chosen
Indicates that one entity is the origin, source, or starting point of the protagonist in a narrative or story.
-
B.
characterOrigin
Indicates the source, background, or initial context from which a character originates.
-
C.
protagonistBasedOn
Indicates that a fictional work’s main character is modeled on, inspired by, or derived from a particular real or fictional person or entity.
-
D.
protagonistType
Indicates the role or category that the main character (protagonist) of a story or scenario belongs to.
-
E.
featuresProtagonistOccupation
Indicates that the work’s main character has a specified occupation or job role.
- 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_69c00879e8048190b690717d19c5bc03 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c0573f17088190a728f1c290cc9d1d |
completed | March 22, 2026, 8:55 p.m. |
| PD | Predicate disambiguation | batch_69c049f031408190b08b2766237c5dd0 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:10 p.m.