Triple
T18834481
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nic |
E460621
|
entity |
| Predicate | familyLifeStatusAtStart |
P120622
|
FINISHED |
| Object | stable |
—
|
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: stable | Statement: [Nic, familyLifeStatusAtStart, stable]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: familyLifeStatusAtStart Context triple: [Nic, familyLifeStatusAtStart, stable]
-
A.
householdStatus
Indicates the type or condition of a person’s living arrangement within a household, such as their role, membership, or current residency status.
-
B.
parentalStatusAtStart
chosen
Indicates the parental status or condition of a person at the beginning of a specified period, event, or process.
-
C.
familySocialStatus
Indicates the social standing or class position associated with a person’s family within a society.
-
D.
parentsMarriageStatus
Indicates the marital status relationship between an individual’s parents (e.g., married, divorced, separated, never married).
-
E.
macroFamilyStatus
Indicates the broad genealogical relationship between languages or language families at the macro-family level.
- 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_69d8dcf94c288190a06dea029ae4b223 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5a99c1394819095c62eef040e552c |
completed | April 20, 2026, 4:20 a.m. |
| PD | Predicate disambiguation | batch_69e48d1e7dac81909ea1e758c87773c5 |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:56 a.m.