Triple
T28305848
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blue |
E713842
|
entity |
| Predicate | isKnownOnlyByPseudonymTo |
P101515
|
FINISHED |
| Object | Simon Spier |
—
|
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: Simon Spier | Statement: [Blue, isKnownOnlyByPseudonymTo, Simon Spier]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isKnownOnlyByPseudonymTo Context triple: [Blue, isKnownOnlyByPseudonymTo, Simon Spier]
-
A.
pseudonymousProducerIs
Indicates that one entity is the pseudonymous producer (creator operating under a pseudonym) of another entity.
-
B.
revealedAsPseudonymIn
Indicates that one identity or name is disclosed or recognized as a pseudonym within a particular context, work, or source.
-
C.
usedPseudonym
Indicates that an entity performed an action or participated in a context under a name that was not their real or primary identity.
-
D.
pseudonymousAttribution
Indicates that an action, work, or statement is attributed to an entity using a pseudonym rather than their real identity.
-
E.
unawareOfTrueIdentityOf
chosen
Indicates that one entity does not know or recognize the real or actual identity of another entity.
- 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_69efb5256afc8190b9322d25c3ae6320 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f644b6b558819095c70a2eb49f1853 |
completed | May 2, 2026, 6:38 p.m. |
| PD | Predicate disambiguation | batch_69f641e0fde08190bf06a1c5b388aa84 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 27, 2026, 11:37 p.m.