Triple
T38226699
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WO-2 |
E1012163
|
entity |
| Predicate | hasNATOCodingScheme |
P182868
|
FINISHED |
| Object | OR |
—
|
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: OR | Statement: [WO-2, hasNATOCodingScheme, OR]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNATOCodingScheme Context triple: [WO-2, hasNATOCodingScheme, OR]
-
A.
hasCodeScheme
Indicates that something is associated with or organized according to a particular coding or classification scheme.
-
B.
hasFeatureCodeSystem
chosen
Indicates that a feature is associated with, or defined according to, a particular code system or coding scheme.
-
C.
hasStructureCode
Indicates that an entity is associated with a specific structural identifier or code that defines its organization or configuration.
-
D.
hasNOCCode
Indicates that an entity is associated with a specific National Occupational Classification (NOC) code that categorizes its occupation or job type.
-
E.
hasStandardCode
Indicates that an entity is associated with a recognized standard code that formally identifies or classifies it.
- 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_69f76dd25e0c81909f2abd0803e5e3ee |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ffc704e1e88190884928a6a5c55a87 |
completed | May 9, 2026, 11:45 p.m. |
| PD | Predicate disambiguation | batch_69ffc6b483d881908ad872e25fa6abc5 |
completed | May 9, 2026, 11:43 p.m. |
Created at: May 3, 2026, 4:30 p.m.