Triple
T2848784
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United Nations Security Council Resolution 715 |
E63042
|
entity |
| Predicate | verificationType |
P4965
|
FINISHED |
| Object | on-site inspections |
—
|
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: on-site inspections | Statement: [United Nations Security Council Resolution 715, verificationType, on-site inspections]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: verificationType Context triple: [United Nations Security Council Resolution 715, verificationType, on-site inspections]
-
A.
confirmationMethod
chosen
Indicates the means or process by which something is verified, validated, or confirmed as true or accepted.
-
B.
credentialType
Indicates the specific kind or category of credential associated with an entity or relationship.
-
C.
validityType
Indicates the specific kind or category of validity that characterizes how or under what conditions something is considered valid.
-
D.
dataTypeVerified
Indicates that the data’s type has been checked and confirmed to match the expected or required type.
-
E.
authenticationType
Indicates the method or mechanism used to verify and confirm an entity’s identity in an interaction or system.
- 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_69ab4c407c408190857d25e027155ce9 |
completed | March 6, 2026, 9:50 p.m. |
| NER | Named-entity recognition | batch_69abdf41ac24819087c5b72e3b84117c |
completed | March 7, 2026, 8:18 a.m. |
| PD | Predicate disambiguation | batch_69abdd0e86808190bcefffafbd3cd441 |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 10:02 p.m.