Triple
T12509433
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schmiedeleut |
E299034
|
entity |
| Predicate | hasColonyStructure |
P105334
|
FINISHED |
| Object | communal ownership of property |
—
|
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: communal ownership of property | Statement: [Schmiedeleut, hasColonyStructure, communal ownership of property]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasColonyStructure Context triple: [Schmiedeleut, hasColonyStructure, communal ownership of property]
-
A.
hasPermanentStructures
Indicates that one entity possesses or contains long-lasting, fixed physical structures associated with it.
-
B.
colonyOf
Indicates that one entity is a colony belonging to, founded by, or politically dependent on another entity.
-
C.
hostsColonyOf
Indicates that one entity serves as the living site or environment in which a colony of another entity resides or is established.
-
D.
operatedInColony
Indicates that an entity conducted operations or activities within a specific colony.
-
E.
colonyStatus
Indicates the political or administrative condition of a territory in relation to a colonizing power, such as whether it is a colony, former colony, or non-colonial.
- 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_69d6ada4cd388190ae3bbf83ff87057a |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d954b867dc8190af8a70f797e4d133 |
completed | April 10, 2026, 7:51 p.m. |
| PD | Predicate disambiguation | batch_69d954096af88190b6be81b008c82139 |
completed | April 10, 2026, 7:48 p.m. |
| PDg | Predicate description generation | batch_69d954b715fc819091fa84430be46273 |
completed | April 10, 2026, 7:51 p.m. |
Created at: April 8, 2026, 9:57 p.m.