Triple
T26616623
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elijah Price |
E668077
|
entity |
| Predicate | closeRelation |
P49697
|
FINISHED |
| Object | Mrs. Price |
—
|
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: Mrs. Price | Statement: [Elijah Price, closeRelation, Mrs. Price]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: closeRelation Context triple: [Elijah Price, closeRelation, Mrs. Price]
-
A.
closeRelationship
chosen
Indicates a strong, intimate, or emotionally significant bond between two entities, suggesting familiarity, trust, and frequent or meaningful interaction.
-
B.
closeAssociation
Indicates a strong, ongoing relationship or connection between two entities, typically involving frequent interaction, mutual influence, or shared context.
-
C.
closeAssociateFamily
Indicates a close, family-level association or relationship between the entities, akin to that of immediate or very trusted extended family members.
-
D.
closeAlly
Indicates a strong, trusted alliance or partnership between two entities, characterized by mutual support and cooperation.
-
E.
relationshipEnd
Indicates that a previously existing relationship between entities has been terminated or has come to an end.
- 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_69ee9cfe16088190a3dddd68e3c7b1ea |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f657f653448190a945b4751af8507d |
completed | May 2, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69f6575ba12081909396036f78757a76 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 27, 2026, 2:19 a.m.