Triple
T29861055
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Burnett family |
E758315
|
entity |
| Predicate | historicOccupation |
P128477
|
FINISHED |
| Object | landowners |
—
|
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: landowners | Statement: [Burnett family, historicOccupation, landowners]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicOccupation Context triple: [Burnett family, historicOccupation, landowners]
-
A.
occupationPeriod
Indicates the time span during which an entity holds or held a particular occupation or role.
-
B.
ethnicHistory
Indicates a relationship where one entity documents, describes, or is associated with the historical development, experiences, or heritage of an ethnic group.
-
C.
historicalHolderOccupation
chosen
Indicates that an entity historically held a particular occupation or professional role.
-
D.
historicallyInhabitedBy
Indicates that a place or region was inhabited by a particular group or population during some period in the past.
-
E.
historicPresence
Indicates that an entity existed, was active, or had a notable presence in a particular place or context during a past time period.
- 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_69f2245b4dec8190b85f664d918a00a5 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69fec00f27988190955de6b6348a4d97 |
completed | May 9, 2026, 5:03 a.m. |
| PD | Predicate disambiguation | batch_69febd52037c8190b475dbd50fdbc13e |
completed | May 9, 2026, 4:51 a.m. |
Created at: April 29, 2026, 5:49 p.m.