Triple
T35016955
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Simon & Marcy |
E1010078
|
entity |
| Predicate | featuresPreIceKingVersionOf |
P183474
|
FINISHED |
| Object | Simon Petrikov |
E1010075
|
NE 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: Simon Petrikov | Statement: [Simon & Marcy, featuresPreIceKingVersionOf, Simon Petrikov]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresPreIceKingVersionOf Context triple: [Simon & Marcy, featuresPreIceKingVersionOf, Simon Petrikov]
-
A.
featuresReimaginedVersionOf
Indicates that something includes or presents a newly interpreted or updated version of another existing work or element.
-
B.
featuresEarlyVersionOf
chosen
Indicates that something includes or presents an earlier or preliminary version of another thing.
-
C.
featuresIn
Indicates that an entity appears or plays a role within another entity, such as a person or element being included in a work, event, or context.
-
D.
featuresPrincess
Indicates that something includes or prominently presents a princess as a central element or character.
-
E.
hasIceFeature
Indicates that one entity possesses, contains, or is characterized by an ice-related feature or formation.
- F. None of above.
Provenance (4 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_69f76dcc3ac8819096a3ed52f5fa2523 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3819c49378819088445c224d3f9f0f |
completed | June 21, 2026, 5:05 p.m. |
| PD | Predicate disambiguation | batch_6a0379ff1ba081908eda86acefcf69fb |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:01 p.m.