Triple
T33506369
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anton |
E858121
|
entity |
| Predicate | familyRelationshipStatus |
P187072
|
FINISHED |
| Object | strained |
—
|
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: strained | Statement: [Anton, familyRelationshipStatus, strained]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: familyRelationshipStatus Context triple: [Anton, familyRelationshipStatus, strained]
-
A.
maritalRelations
Indicates a legally or socially recognized spousal relationship or marriage-based connection between two entities.
-
B.
relationshipToSpouse
Indicates the specific familial or social role one person holds in relation to their spouse (e.g., husband, wife, partner).
-
C.
familySocialStatus
Indicates the social standing or class position associated with a person’s family within a society.
-
D.
politicalRelationship
Indicates a relationship in which entities are connected through political roles, alliances, affiliations, or interactions within a political context.
-
E.
relationshipToParents
Indicates the type or nature of a person's familial relationship to their parents.
- 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_69f3497721848190978fbee5e0a526f8 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fb3425666081908916fcbf3b5dd907 |
completed | May 6, 2026, 12:29 p.m. |
| PD | Predicate disambiguation | batch_69fb2f5f3164819099429c2cc3d24e01 |
completed | May 6, 2026, 12:09 p.m. |
| PDg | Predicate description generation | batch_69fb3424724c8190ba55ecf66fa0b171 |
completed | May 6, 2026, 12:29 p.m. |
Created at: May 1, 2026, 1:38 a.m.