Triple
T5351363
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heed |
E102585
|
entity |
| Predicate | hasRelationshipTypeWithChristine |
P10690
|
FINISHED |
| Object | lifelong bond |
—
|
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: lifelong bond | Statement: [Heed, hasRelationshipTypeWithChristine, lifelong bond]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRelationshipTypeWithChristine Context triple: [Heed, hasRelationshipTypeWithChristine, lifelong bond]
-
A.
relationshipType
chosen
Indicates the specific kind of relationship that exists between two or more entities.
-
B.
inRelationshipWith
Indicates that two entities are mutually involved in a defined personal, romantic, or partnership relationship with each other.
-
C.
hasMaritalRelationshipType
Indicates the specific type or nature of the marital relationship that exists between two entities.
-
D.
hasFamilialTieTo
Indicates a relationship where two entities are connected by family bonds, such as by blood, marriage, or adoption.
-
E.
relationshipToLaurie
Indicates the specific type of relationship or connection that an entity has to Laurie.
- 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_69bd43d8f7248190b64c140734b5c9a8 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd861188ac81908ef2b1f25cc6c864 |
completed | March 20, 2026, 5:38 p.m. |
| PD | Predicate disambiguation | batch_69bd845c6f108190832a8d14b356368a |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:01 p.m.