Triple
T28441801
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | No Sudden Move |
E715730
|
entity |
| Predicate | directorPseudonymUsed |
P126881
|
FINISHED |
| Object | Peter Andrews |
—
|
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: Peter Andrews | Statement: [No Sudden Move, directorPseudonymUsed, Peter Andrews]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: directorPseudonymUsed Context triple: [No Sudden Move, directorPseudonymUsed, Peter Andrews]
-
A.
pseudonymOfArtist
chosen
Indicates that one name is a pseudonym used by an artist as an alternative to their real or primary name.
-
B.
revealedAsPseudonymIn
Indicates that one identity or name is disclosed or recognized as a pseudonym within a particular context, work, or source.
-
C.
coAppearsWithPseudonym
Indicates that an entity appears together with another entity that is identified or referenced by a pseudonym in the same context or source.
-
D.
directorAssociatedWith
Indicates a relationship where a director is professionally connected to, responsible for, or involved with a particular entity (such as a work, organization, or project).
-
E.
pseudonymCoinedBy
Indicates that a particular pseudonym was created or invented by a specific agent or source.
- 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_69efd6b44550819094ae991b553d9fc3 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f7805ce6208190ac6dbd9c97989978 |
completed | May 3, 2026, 5:05 p.m. |
| PD | Predicate disambiguation | batch_69f77956ec648190ba4fb7e9d83fd107 |
completed | May 3, 2026, 4:35 p.m. |
Created at: April 28, 2026, 1:46 a.m.