Triple
T33727629
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Freddie Borden |
E864186
|
entity |
| Predicate | sharesLifeWith |
P151025
|
FINISHED |
| Object | Alfred Borden |
—
|
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: Alfred Borden | Statement: [Freddie Borden, sharesLifeWith, Alfred Borden]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesLifeWith Context triple: [Freddie Borden, sharesLifeWith, Alfred Borden]
-
A.
sharesLifeLinkWith
Indicates that two entities are bound so that changes to one’s life state (such as damage, death, or survival) directly and correspondingly affect the other.
-
B.
sharesLifeboatWith
Indicates that two or more entities are occupying or using the same lifeboat together.
-
C.
sharesLifewaysAmong
Indicates that multiple entities participate in and transmit common cultural practices, values, or ways of living among one another.
-
D.
sharesFateWith
chosen
Indicates that two or more entities are bound to experience the same outcome, destiny, or consequences.
-
E.
sharedLaterLifeWith
Indicates that two entities spent a significant portion of their later life period together, sharing circumstances, experiences, or close association during that time.
- 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_69f3498a64cc8190b4b414c67b280d93 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ffb97b8ff8819088b105d99a0820c9 |
completed | May 9, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69ffb88ef7388190a710120ed76edc0e |
completed | May 9, 2026, 10:43 p.m. |
Created at: May 1, 2026, 1:44 a.m.