Triple
T8934965
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Poe family |
E212752
|
entity |
| Predicate | hasRelativeRelationship |
P27845
|
FINISHED |
| Object | Edgar Allan Poe – son of David Poe Jr. |
—
|
LITERAL FINISHED |
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: Edgar Allan Poe – son of David Poe Jr. | Statement: [Poe family, hasRelativeRelationship, Edgar Allan Poe – son of David Poe Jr.]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRelativeRelationship Context triple: [Poe family, hasRelativeRelationship, Edgar Allan Poe – son of David Poe Jr.]
-
A.
hasRelation
Indicates that there exists some specified relationship or association between two entities.
-
B.
hasRelativeRole
chosen
Indicates that one entity holds a familial or kinship-based role in relation to another entity.
-
C.
hasRelativeLocation
Indicates that one entity is positioned in space in relation to another entity’s location.
-
D.
hasNeighborRelationshipWith
Indicates that one entity is located adjacent to or directly next to another entity, sharing a neighbor relationship.
-
E.
laterRelationWith
Indicates that one entity stands in a temporal relationship to another such that it occurs or exists at a later time than the other.
- 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_69ca8395c438819087d7cb844ab5990c |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc669138b48190a6bb4968f029a69e |
completed | April 1, 2026, 12:28 a.m. |
| PD | Predicate disambiguation | batch_69cc5ed3286c8190a21de2ee11f2639f |
completed | March 31, 2026, 11:54 p.m. |
Created at: March 30, 2026, 6:58 p.m.