Triple
T10057598
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | zu-yong-diao system |
E208899
|
entity |
| Predicate | socialGroupTaxed |
P91878
|
FINISHED |
| Object | peasant households |
—
|
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: peasant households | Statement: [zu-yong-diao system, socialGroupTaxed, peasant households]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: socialGroupTaxed Context triple: [zu-yong-diao system, socialGroupTaxed, peasant households]
-
A.
socialGroupInvolved
Indicates that a particular social group participates in, is affected by, or is otherwise involved in the specified event or situation.
-
B.
hasSocialGroup
Indicates that an entity belongs to, is associated with, or participates in a particular social group or community.
-
C.
representedGroups
Indicates that an entity serves as an official or recognized representative for one or more groups.
-
D.
customerGroup
Indicates a relationship in which an entity belongs to, is classified under, or is associated with a particular group of customers.
-
E.
typicalGroup
Indicates that the subject belongs to or represents a standard, characteristic, or commonly occurring group associated with the object.
- 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_69ca836094408190a36a1ea7e9a86fcd |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cdcfaf7700819084dedf7b63e789c1 |
completed | April 2, 2026, 2:08 a.m. |
| PD | Predicate disambiguation | batch_69cd4b92573481909389bc6148ae7ea8 |
completed | April 1, 2026, 4:45 p.m. |
| PDg | Predicate description generation | batch_69cd4f8d9b888190b8067bd916dae773 |
completed | April 1, 2026, 5:02 p.m. |
Created at: March 30, 2026, 8:57 p.m.