Triple
T6781522
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GF |
E155692
|
entity |
| Predicate | usedInDataStandards |
P60418
|
FINISHED |
| Object | country and territory identification |
—
|
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: country and territory identification | Statement: [GF, usedInDataStandards, country and territory identification]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInDataStandards Context triple: [GF, usedInDataStandards, country and territory identification]
-
A.
reportingStandard
Indicates that one entity uses, follows, or is governed by a particular reporting standard defined by another entity.
-
B.
standardizedIn
Indicates that something has been formally defined, regulated, or made uniform within a particular standard, framework, or jurisdiction.
-
C.
classificationUsedBy
chosen
Indicates that a particular classification system or scheme is employed or applied by a given entity.
-
D.
usedInLabeling
Indicates that something is employed or applied as part of a labeling process or activity.
-
E.
usedInUNStatistics
Indicates that something is employed or referenced within official United Nations statistical data, classifications, or reporting.
- 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_69c688162bf8819088b664b5c3b5be7a |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d26c621c8190a6eddc0d395e13e4 |
completed | March 27, 2026, 6:54 p.m. |
| PD | Predicate disambiguation | batch_69c6d095dcac8190bb9b943f50a7f885 |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:14 p.m.