Triple
T32508906
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sprite (MCU) |
E830875
|
entity |
| Predicate | trueOrigin |
P58596
|
FINISHED |
| Object | created by Arishem the Judge |
—
|
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: created by Arishem the Judge | Statement: [Sprite (MCU), trueOrigin, created by Arishem the Judge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trueOrigin Context triple: [Sprite (MCU), trueOrigin, created by Arishem the Judge]
-
A.
originallyProclaimed
Indicates that an entity first formally announced, declared, or made known another entity or statement at an earlier point in time.
-
B.
alternativeOrigin
Indicates that an entity has a different or secondary source, starting point, or provenance compared to its primary or usual origin.
-
C.
originalFor
chosen
Indicates that one entity serves as the source, basis, or prototype from which another entity is derived, adapted, or created.
-
D.
traditionalOrigin
Indicates that something comes from, or is rooted in, a long-established cultural or customary source or practice.
-
E.
originallyIn
Indicates that something first appeared, was created, or was initially located within a particular context, source, or place.
- 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_69f3492318348190ba37fb6b5f1d67f4 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c44d21648190ada905d52e251b1f |
completed | May 3, 2026, 3:43 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2a14b081908162923dfbf0a6f4 |
completed | May 3, 2026, 3:12 a.m. |
Created at: May 1, 2026, 1 a.m.