Triple
T4503469
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Friendly Relations Declaration |
E101275
|
entity |
| Predicate | regionOfRelevance |
P32691
|
FINISHED |
| Object | worldwide |
—
|
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: worldwide | Statement: [Friendly Relations Declaration, regionOfRelevance, worldwide]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionOfRelevance Context triple: [Friendly Relations Declaration, regionOfRelevance, worldwide]
-
A.
coreRegionOf
Indicates that one entity constitutes the central or most essential part of another entity’s structure, area, or domain.
-
B.
regionContext
chosen
Indicates the broader geographic or spatial setting within which an entity, event, or relationship is situated or interpreted.
-
C.
region1
Indicates that one entity is the first or primary region associated with, containing, or encompassing another entity.
-
D.
mentionsRegion
Indicates that one entity explicitly refers to or cites a specific geographic region in its content or context.
-
E.
isRegionOf
Indicates that one entity is a geographic or administrative region belonging to, contained within, or associated with another entity.
- 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_69bd43d175248190894dc58b5b395c26 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd56fca7d4819081deb34628e04f00 |
completed | March 20, 2026, 2:17 p.m. |
| PD | Predicate disambiguation | batch_69bd521671688190bc655d25fa77eba2 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:01 p.m.