Triple
T32018103
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Parr |
E817599
|
entity |
| Predicate | fullNameInUniverse |
P16
|
FINISHED |
| Object | John Jackson Parr |
—
|
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 Jackson Parr | Statement: [John Parr, fullNameInUniverse, John Jackson Parr]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fullNameInUniverse Context triple: [John Parr, fullNameInUniverse, John Jackson Parr]
-
A.
fullNameInNewspeak
Indicates that an entity’s full name is expressed or recorded using the Newspeak language.
-
B.
characterFullName
Indicates that the predicate specifies the complete, formal name of a character.
-
C.
hasFullNameInCanon
Indicates that an entity’s complete, official name is explicitly established within the canonical source material.
-
D.
namedAfterInUniverse
Indicates that one entity is, within the fictional or narrative universe, explicitly stated or implied to be named after another entity.
-
E.
fullName
chosen
Indicates that an entity has a complete personal name, typically combining given name(s) and family name into a single string.
- 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_69f348f9e5d081908cc3f57c4942af52 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b49436b0819094e21603054d05d4 |
completed | May 3, 2026, 2:36 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a7bdb481908d16a32f49e38c2c |
completed | May 3, 2026, 2:32 a.m. |
Created at: May 1, 2026, 12:16 a.m.