Triple
T35290637
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hagen |
E1019212
|
entity |
| Predicate | familyStatusInText |
P189425
|
FINISHED |
| Object | unmarried |
—
|
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: unmarried | Statement: [Hagen, familyStatusInText, unmarried]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: familyStatusInText Context triple: [Hagen, familyStatusInText, unmarried]
-
A.
familySocialStatus
Indicates the social standing or class position associated with a person’s family within a society.
-
B.
currentFamilyStatus
chosen
Indicates the present state or condition of an entity’s family situation or relationships.
-
C.
familyDescription
Indicates a descriptive statement that characterizes or summarizes the nature, structure, or dynamics of a family relationship.
-
D.
macroFamilyStatus
Indicates the broad genealogical relationship between languages or language families at the macro-family level.
-
E.
familyType
Indicates the specific familial relationship or category that characterizes how the related entities are connected as family.
- 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_69f76de7eedc8190a3bdc64ebbc05b42 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fce7671f108190bf3ebf54339068b5 |
completed | May 7, 2026, 7:26 p.m. |
| PD | Predicate disambiguation | batch_69fce5b5a84c81908ac1b5b9f08d48d0 |
completed | May 7, 2026, 7:19 p.m. |
Created at: May 3, 2026, 4:03 p.m.