Triple
T31200736
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Lange |
E795467
|
entity |
| Predicate | realNameOfAuthor |
P9233
|
FINISHED |
| Object | John Michael Crichton |
—
|
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: John Michael Crichton | Statement: [John Lange, realNameOfAuthor, John Michael Crichton]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: realNameOfAuthor Context triple: [John Lange, realNameOfAuthor, John Michael Crichton]
-
A.
authorRealNameOfCreator
Indicates that a person’s real, legal, or birth name is the true identity behind a creator who may be known by a pseudonym or handle.
-
B.
authorName
Indicates the name associated with the person or entity that authored a given work or resource.
-
C.
realName
chosen
Indicates that one entity is the actual, full, or birth name of another entity, which may be known by an alias, nickname, or alternate identity.
-
D.
hasAuthorRealName
Indicates that an entity (such as a work or pseudonym) is associated with the actual, legal name of its author.
-
E.
alsoKnownAsRealAuthor
Indicates that an entity is an alternative or alias name identifying the same individual who is the actual (real) author of a work.
- 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_69f224d8c6608190b7882466521f62be |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69bc2ca808190876e5cb05012dbfc |
completed | May 3, 2026, 12:50 a.m. |
| PD | Predicate disambiguation | batch_69f696673214819094350e1d2648ef34 |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 9:09 p.m.