Triple
T25048030
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Olmsted family |
E627297
|
entity |
| Predicate | hasProfessionalDynasty |
P166108
|
FINISHED |
| Object | Olmsted Brothers |
—
|
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: Olmsted Brothers | Statement: [Olmsted family, hasProfessionalDynasty, Olmsted Brothers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProfessionalDynasty Context triple: [Olmsted family, hasProfessionalDynasty, Olmsted Brothers]
-
A.
hasNotableDynastyMember
Indicates that a dynasty includes at least one member who is historically or culturally notable.
-
B.
hasDynast
Indicates that an entity is associated with or ruled by a particular dynasty.
-
C.
hasDynasticConnections
Indicates that one entity is related to another through familial or hereditary ties between ruling or noble dynasties.
-
D.
hasFamilyBackgroundIn
Indicates that an entity comes from, or is associated with, a particular familial or ancestral background.
-
E.
hasLongtimePoliticalFamily
Indicates that an entity has close family members who have been involved in politics for an extended period of time.
- F. None of above. chosen
Provenance (4 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_69e2ff2b4c80819087c916b2b16241b9 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f66003a3f48190a2ba6da5aafbb5cb |
completed | May 2, 2026, 8:35 p.m. |
| PD | Predicate disambiguation | batch_69f65c1f94ac8190bc6fbc7916fc0d82 |
completed | May 2, 2026, 8:18 p.m. |
| PDg | Predicate description generation | batch_69f65f75ac608190a62cd6afce14f68e |
completed | May 2, 2026, 8:32 p.m. |
Created at: April 18, 2026, 6:08 a.m.