Triple
T9053335
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | People's Committees system |
E216937
|
entity |
| Predicate | officialTerminology |
P86109
|
FINISHED |
| Object | people's authority |
—
|
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: people's authority | Statement: [People's Committees system, officialTerminology, people's authority]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: officialTerminology Context triple: [People's Committees system, officialTerminology, people's authority]
-
A.
officialTermLanguage
Indicates the language in which an official term is formally expressed or defined.
-
B.
languageTerm
Indicates that one entity is a linguistic expression (word, phrase, or term) used to denote or label the other entity.
-
C.
usesTerminologyFrom
Indicates that one entity adopts or incorporates the specialized terms or vocabulary originating from another entity or source.
-
D.
terminologyNote
Indicates that there is an explanatory note or comment clarifying the use, meaning, or nuances of a specific term in the relationship.
-
E.
termLanguage
Indicates the language in which a given term is expressed or defined.
- 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_69ca83d362e88190ae44b4e4dc194209 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc7a71a9d88190949ef9dc6816d6ab |
completed | April 1, 2026, 1:52 a.m. |
| PD | Predicate disambiguation | batch_69cc5ee566b081909e3cdaf551dbd0ec |
completed | March 31, 2026, 11:55 p.m. |
| PDg | Predicate description generation | batch_69cc5f4f1cb48190a025d1b3d8d7a790 |
completed | March 31, 2026, 11:57 p.m. |
Created at: March 30, 2026, 7:10 p.m.