Triple
T24934537
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | La Trobe family |
E623277
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Australian historical family |
C35294
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: Australian historical family Context triple: [La Trobe family, instanceOf, Australian historical family]
-
A.
Australian family
chosen
An Australian family is a social unit typically consisting of individuals related by blood, marriage, or partnership who share a household or maintain close kinship ties within the cultural, legal, and social context of Australia.
-
B.
Australian historical event
An Australian historical event is a significant occurrence in Australia’s past that has shaped the nation’s political, social, cultural, or economic development.
-
C.
colonial-era family
A colonial-era family is a household unit living during a period of colonization, typically consisting of parents, children, and sometimes extended relatives, whose daily life, roles, and relationships are shaped by the social, economic, and political structures of the colonial system.
-
D.
British landed family
A British landed family is a socially prominent household that historically derives its status, wealth, and influence from the long-term ownership and management of rural estates and agricultural land in Britain.
-
E.
Australian person
An Australian person is an individual who is a citizen or resident of Australia, typically associated with its diverse multicultural society, English language use, and cultural practices influenced by Indigenous, British, and broader global traditions.
- F. None of above.
Provenance (1 batch)
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_69e2fac6b5a48190a1c38857f00915a9 |
completed | April 18, 2026, 3:30 a.m. |
Created at: April 18, 2026, 5:30 a.m.