Triple
T22475441
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISO/IEC JTC 1/SC 2/WG 3 |
E555615
|
entity |
| Predicate | areaWithinSC2 |
P46950
|
FINISHED |
| Object | coded character sets and encoding |
—
|
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: coded character sets and encoding | Statement: [ISO/IEC JTC 1/SC 2/WG 3, areaWithinSC2, coded character sets and encoding]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: areaWithinSC2 Context triple: [ISO/IEC JTC 1/SC 2/WG 3, areaWithinSC2, coded character sets and encoding]
-
A.
regionInGame
Indicates that a specific region or area exists within or is part of a particular game.
-
B.
scoutingArea
Indicates that an entity is actively exploring or surveying a specified area, typically to gather information or assess conditions there.
-
C.
realmWithin
chosen
Indicates that one realm or domain is contained inside, or exists as a subset of, another realm or domain.
-
D.
regionAtStake
Indicates that a specific geographic or political area is the subject of contention, risk, or negotiation within a given situation or interaction.
-
E.
areaOfSupport
Indicates the spatial region or domain within which an entity provides support, assistance, or backing to another.
- 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_69e11e52c2048190952dc5df209b9bed |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15be3930c8190ba967196df7e083f |
completed | April 29, 2026, 1:16 a.m. |
| PD | Predicate disambiguation | batch_69e898b6eee08190ba673a0ee329e671 |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:49 p.m.