Triple
T37274794
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VEMR |
E924615
|
entity |
| Predicate | codingAuthority |
P117940
|
FINISHED |
| Object | International Civil Aviation Organization |
—
|
NE NERFINISHED |
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 Civil Aviation Organization | Statement: [VEMR, codingAuthority, International Civil Aviation Organization]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: codingAuthority Context triple: [VEMR, codingAuthority, International Civil Aviation Organization]
-
A.
codingDomain
Indicates that an entity operates within, pertains to, or is characterized by a particular domain or field of coding or programming.
-
B.
codeNature
Indicates that one entity characterizes or specifies the type, category, or inherent nature of another entity, often in a coded or standardized form.
-
C.
codingParadigm
Indicates the programming paradigm or style (e.g., object-oriented, functional, procedural) that characterizes how code is structured and organized in a given context.
-
D.
codifiedUnderAuthority
chosen
Indicates that something has been formally established, defined, or recorded according to the rules or power of a specific authority.
-
E.
codeOn
Indicates that one entity writes, develops, or modifies software using or for another entity (such as a platform, project, or codebase).
- 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_69f76eacdd8c819094080d3991e6d37c |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb78cbef988190b8f79d946b46e6b2 |
completed | May 6, 2026, 5:22 p.m. |
| PD | Predicate disambiguation | batch_69fb5a9ac5a08190b24ef308963fc52b |
completed | May 6, 2026, 3:13 p.m. |
Created at: May 3, 2026, 4:16 p.m.