Triple
T17980411
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pichatur |
E449586
|
entity |
| Predicate | hasMandalStatus |
P129989
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Pichatur, hasMandalStatus, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMandalStatus Context triple: [Pichatur, hasMandalStatus, yes]
-
A.
hasMandate
Indicates that an entity is officially authorized or required to perform a specific role, action, or set of responsibilities.
-
B.
hasUNMandateType
Indicates the specific type or category of United Nations mandate under which an action, mission, or operation is authorized or conducted.
-
C.
hasMAD
Indicates that an entity possesses or is associated with a specific MAD (e.g., a minimum acceptable distance, mean absolute deviation, or similarly defined MAD-related measure).
-
D.
hasMast
Indicates that an object possesses or is equipped with a mast as part of its structure.
-
E.
hasUnitStatus
Indicates that an entity is associated with a particular operational or condition status as a unit.
- 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_69d8b9f9927c8190a006110c8b996e61 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e4b202aab88190b44851808c75a848 |
completed | April 19, 2026, 10:44 a.m. |
| PD | Predicate disambiguation | batch_69e3f8fa62688190a5d5c361ab896256 |
completed | April 18, 2026, 9:34 p.m. |
| PDg | Predicate description generation | batch_69e42d8d68288190a05dc5d7803cf823 |
completed | April 19, 2026, 1:19 a.m. |
Created at: April 10, 2026, 10:22 a.m.