Triple
T27658119
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WG 14 |
E697046
|
entity |
| Predicate | standardizationBodyType |
P168952
|
FINISHED |
| Object | international |
—
|
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: international | Statement: [WG 14, standardizationBodyType, international]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardizationBodyType Context triple: [WG 14, standardizationBodyType, international]
-
A.
establishedBodyType
Indicates that an entity has formally created, founded, or set up a particular organizational body or structure.
-
B.
establishesBodyType
Indicates that an entity defines or sets the physical or structural body type of another entity.
-
C.
managementBodyType
Indicates the type or category of governing or management body responsible for overseeing an entity.
-
D.
primaryBodyType
Indicates the main physical form or category that characterizes an entity’s overall body structure or composition.
-
E.
parentBodyType
Indicates that one entity has a body type that serves as the parent or base classification from which another entity's body type is derived or organized.
- 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_69ef590b85a4819083ec7c12bd3c9c10 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f67866e9248190b7ba218f9ca2ae8d |
completed | May 2, 2026, 10:19 p.m. |
| PD | Predicate disambiguation | batch_69f675fd59608190b246383435e68fce |
completed | May 2, 2026, 10:09 p.m. |
| PDg | Predicate description generation | batch_69f676c35f3481909b9ba18a5662d6ce |
completed | May 2, 2026, 10:12 p.m. |
Created at: April 27, 2026, 2:35 p.m.