Triple
T37255911
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flintstone family |
E924124
|
entity |
| Predicate | spouseOfHouseholdHead |
P45366
|
FINISHED |
| Object | Wilma Flintstone |
—
|
NE NERFINISHED |
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: Wilma Flintstone | Statement: [Flintstone family, spouseOfHouseholdHead, Wilma Flintstone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spouseOfHouseholdHead Context triple: [Flintstone family, spouseOfHouseholdHead, Wilma Flintstone]
-
A.
spouseOfHead
chosen
Indicates that one person is the married partner of the individual who holds the position of head (e.g., head of a household, organization, or state).
-
B.
spouseInFamily
Indicates that a person is a spouse (married partner) within the context of a specific family unit.
-
C.
spouseMember
Indicates that one entity is the spouse (married partner) of another entity.
-
D.
spouseOfWork
Indicates that one person is the spouse of another specifically in the context of their workplace or professional environment.
-
E.
spouseOfType
Indicates that one entity is the spouse of another, specifying the type or role of that spousal relationship.
- 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_69f76eabd6c481909d414a80a1345c98 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69feaa483fcc81909d8a46b38a8717bf |
completed | May 9, 2026, 3:30 a.m. |
| PD | Predicate disambiguation | batch_69fea8c9d45c81908ccc8619e5fefac1 |
completed | May 9, 2026, 3:23 a.m. |
Created at: May 3, 2026, 4:15 p.m.