Triple
T31243033
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Washington Post Company |
E796610
|
entity |
| Predicate | formerControllingFamily |
P156383
|
FINISHED |
| Object | Meyer family |
—
|
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: Meyer family | Statement: [The Washington Post Company, formerControllingFamily, Meyer family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerControllingFamily Context triple: [The Washington Post Company, formerControllingFamily, Meyer family]
-
A.
formerOwnerFamily
chosen
Indicates that a member of the subject’s family previously owned the object but no longer does.
-
B.
governingFamilyOf
Indicates that one family holds ruling or sovereign authority over a particular territory, state, or political entity.
-
C.
formerRulingClan
Indicates that a clan previously held ruling power or authority over a group, territory, or polity but no longer does so.
-
D.
familyOf
Indicates a familial relationship exists between the entities, such as by blood, marriage, or adoption.
-
E.
successorFamily
Indicates that one family succeeds or follows another family in a lineage, role, position, or ownership.
- 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_69f224dc84d0819081f1cb6f9127e6b1 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69ff2636e2bc8190bba91eff91431c6e |
completed | May 9, 2026, 12:19 p.m. |
| PD | Predicate disambiguation | batch_69ff25c65be48190868480d94e1c4e89 |
completed | May 9, 2026, 12:17 p.m. |
Created at: April 29, 2026, 9:11 p.m.