Triple
T27295893
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jerome Eugene Morrow |
E688762
|
entity |
| Predicate | hasAliasUsedByVincent |
P170374
|
FINISHED |
| Object | Jerome Morrow |
—
|
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: Jerome Morrow | Statement: [Jerome Eugene Morrow, hasAliasUsedByVincent, Jerome Morrow]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAliasUsedByVincent Context triple: [Jerome Eugene Morrow, hasAliasUsedByVincent, Jerome Morrow]
-
A.
usesAliasTo
Indicates that one entity employs an alternative name or identifier to refer to or represent another entity.
-
B.
usesAliasFor
Indicates that one entity employs an alternative name or identifier to refer to another entity.
-
C.
usesAliasWith
Indicates that one entity employs or operates under an alternative name or identifier in association with another entity.
-
D.
usedByAlias
Indicates that something is utilized, referenced, or accessed through an alternative name or alias.
-
E.
hasAliasUser
Indicates that a user is known or referred to by an alternative name or identifier.
- F. None of above. chosen
Provenance (4 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_69f69063edbc81909e7735954aabee0b |
completed | May 3, 2026, 12:01 a.m. |
| PD | Predicate disambiguation | batch_69f68b78f29481908cc8f390496dee97 |
completed | May 2, 2026, 11:40 p.m. |
| PDg | Predicate description generation | batch_69f68f6584a88190a8c4d95c0c84bee9 |
completed | May 2, 2026, 11:57 p.m. |
Created at: April 27, 2026, 11:18 a.m.