Triple
T18749543
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISO correspondent members |
E458490
|
entity |
| Predicate | isStatusOf |
P133403
|
FINISHED |
| Object | national standards body of a non‑member country |
—
|
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: national standards body of a non‑member country | Statement: [ISO correspondent members, isStatusOf, national standards body of a non‑member country]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isStatusOf Context triple: [ISO correspondent members, isStatusOf, national standards body of a non‑member country]
-
A.
hasStatusBasedOn
Indicates that an entity’s status is determined or derived from another condition, event, or entity.
-
B.
typeOfStatus
Indicates the specific status category or condition that an entity is classified as having.
-
C.
definedStatusFor
Indicates that one entity establishes or specifies the status or state assigned to another entity.
-
D.
statusInSI
Indicates that an entity’s status or condition is specified according to the International System of Units (SI) or an SI-based standard.
-
E.
classStatus
Indicates the current academic or enrollment standing of an entity within a class or course context.
- F. None of above. chosen
Provenance (4 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_69d8d394dc308190b6725073f5db324c |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e579eb7350819099d7291207781116 |
completed | April 20, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69e48d0b7b708190877951b6e6cdcbc4 |
completed | April 19, 2026, 8:06 a.m. |
| PDg | Predicate description generation | batch_69e49a9bcc0c81908df3e513fd6762ff |
completed | April 19, 2026, 9:04 a.m. |
Created at: April 10, 2026, 11:51 a.m.