Triple
T758840
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | class G – Geography, Anthropology, Recreation |
E16019
|
entity |
| Predicate | classificationCodeRange |
P8090
|
FINISHED |
| Object | G-GV |
—
|
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: G-GV | Statement: [class G – Geography, Anthropology, Recreation, classificationCodeRange, G-GV]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: classificationCodeRange Context triple: [class G – Geography, Anthropology, Recreation, classificationCodeRange, G-GV]
-
A.
catalogCode
chosen
Indicates that an entity is assigned a specific catalog identifier or code used for classification or reference.
-
B.
numericCode
Indicates that an entity is associated with a specific numerical identifier or classification code.
-
C.
relatedCodeSet
Indicates that one code set is associated with or connected to another code set in a meaningful or defined way.
-
D.
postalCodeRange
Indicates that one entity specifies a contiguous range of postal codes applicable to another entity or context.
-
E.
codificationLevel
Indicates the degree or extent to which something is formally systematized, standardized, or encoded into an explicit set of rules or structures.
- 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_69a493684ee48190bd43b7c78da4aec8 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a67f9778819098d3c144dd26b976 |
completed | March 1, 2026, 8:50 p.m. |
| PD | Predicate disambiguation | batch_69a4a50348088190873a1446db657a78 |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:37 p.m.