Triple
T13941854
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hello, Larry |
E335274
|
entity |
| Predicate | mainCharacterFamilyStatus |
P80421
|
FINISHED |
| Object | Single father |
—
|
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: Single father | Statement: [Hello, Larry, mainCharacterFamilyStatus, Single father]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainCharacterFamilyStatus Context triple: [Hello, Larry, mainCharacterFamilyStatus, Single father]
-
A.
protagonistFamilyStatus
chosen
Indicates the familial role or position that a character holds in relation to the story’s protagonist.
-
B.
macroFamilyStatus
Indicates the broad genealogical relationship between languages or language families at the macro-family level.
-
C.
familySocialStatus
Indicates the social standing or class position associated with a person’s family within a society.
-
D.
householdStatus
Indicates the type or condition of a person’s living arrangement within a household, such as their role, membership, or current residency status.
-
E.
hasFamilyRole
Indicates that one entity holds a specific familial role or position in relation to another entity.
- 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_69d81c6081b88190b53e317c3370c8fe |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2cf6e29881908ddb8efca9a456a3 |
completed | April 14, 2026, 12:03 p.m. |
| PD | Predicate disambiguation | batch_69de05a3ccf88190b45c742db483fa08 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:17 p.m.