Triple
T27295874
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jerome Eugene Morrow |
E688762
|
entity |
| Predicate | providesIdentityTo |
P96087
|
FINISHED |
| Object | Vincent Freeman |
—
|
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: Vincent Freeman | Statement: [Jerome Eugene Morrow, providesIdentityTo, Vincent Freeman]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: providesIdentityTo Context triple: [Jerome Eugene Morrow, providesIdentityTo, Vincent Freeman]
-
A.
publicIdentity
Indicates that an entity’s outward-facing identity or persona is known, presented, or recognized in a public context.
-
B.
subjectIdentity
Indicates that two or more references correspond to the same underlying entity or individual identity.
-
C.
globalIdentity
Indicates that two or more identifiers or representations actually refer to the same underlying global entity or individual.
-
D.
adoptedIdentity
chosen
Indicates that one entity has taken on or assumed the identity, role, or persona of another entity, either formally or informally.
-
E.
hasIdentity
Indicates that one entity is the same as, or is identified as, another specific entity or identifier.
- 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_69ef355a96308190a2bed991525fb278 |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f7117e55908190a67105e92bc4830f |
completed | May 3, 2026, 9:12 a.m. |
| PD | Predicate disambiguation | batch_69f70f380690819090cc34763ba460ed |
completed | May 3, 2026, 9:02 a.m. |
Created at: April 27, 2026, 11:18 a.m.