Triple
T31769945
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amana Society communal system |
E810910
|
entity |
| Predicate | propertySystem |
P175817
|
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: [Amana Society communal system, propertySystem, communal ownership of property]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: propertySystem Context triple: [Amana Society communal system, propertySystem, communal ownership of property]
-
A.
property
Indicates that one entity possesses, is characterized by, or has an attribute or quality associated with another entity.
-
B.
propertyForm
Indicates the specific form, type, or configuration that a property takes within a given context or system.
-
C.
basisProperty
Indicates that one property serves as the foundational or defining basis for another property or characteristic.
-
D.
propertyHeld
Indicates that a particular property is possessed, owned, or controlled by a specified entity.
-
E.
propertyType_id
Indicates a relationship that specifies the type or category of a property associated with an entity.
- 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_69f348e463e08190b902d4819195e1f0 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6d74b20a48190900dda1014cc13a8 |
completed | May 3, 2026, 5:04 a.m. |
| PD | Predicate disambiguation | batch_69f6d26f27dc8190ae426a3e1573933e |
completed | May 3, 2026, 4:43 a.m. |
| PDg | Predicate description generation | batch_69f6d749e7f081909c8196898c4191ad |
completed | May 3, 2026, 5:04 a.m. |
Created at: April 30, 2026, 11:33 p.m.