Triple
T25945486
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United Nations Security Council Resolution 819 |
E653828
|
entity |
| Predicate | declaredStatus |
P46489
|
FINISHED |
| Object | safe area |
—
|
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: safe area | Statement: [United Nations Security Council Resolution 819, declaredStatus, safe area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: declaredStatus Context triple: [United Nations Security Council Resolution 819, declaredStatus, safe area]
-
A.
declared
Indicates that an entity formally announces, states, or proclaims something, often with official or authoritative intent.
-
B.
declaredTo
Indicates that one entity formally made a statement, announcement, or assertion to another specific entity.
-
C.
regulatedStatusOf
Indicates that one entity has regulatory authority or control over the status or condition of another entity.
-
D.
definedStatusFor
Indicates that one entity establishes or specifies the status or state assigned to another entity.
-
E.
designationStatus
chosen
Indicates the current official classification or standing assigned to an entity within a defined system or process.
- F. None of above.
Provenance (3 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_69e7ab40ac788190a771bc499eb1ae5f |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f60464d4988190bc39b78c8e418547 |
completed | May 2, 2026, 2:04 p.m. |
| PD | Predicate disambiguation | batch_69f5afec3e94819080d9ba86cf8c866e |
completed | May 2, 2026, 8:03 a.m. |
Created at: April 22, 2026, 8:43 a.m.