Triple
T738862
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | International Convention relating to Cooperation for the Safety of Air Navigation |
E14997
|
entity |
| Predicate | typeOfParties |
P6384
|
FINISHED |
| Object | sovereign states |
—
|
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: sovereign states | Statement: [International Convention relating to Cooperation for the Safety of Air Navigation, typeOfParties, sovereign states]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfParties Context triple: [International Convention relating to Cooperation for the Safety of Air Navigation, typeOfParties, sovereign states]
-
A.
typicalParty
Indicates that an entity is a usual, standard, or characteristic participant in a given type of event, situation, or relationship.
-
B.
participantType
chosen
Indicates the specific role or category that a participant has within a given event, activity, or relationship.
-
C.
typeOfEvent
Indicates that one entity is classified as a specific kind or category of event.
-
D.
recognizesParty
Indicates that one entity formally acknowledges the existence, status, or legitimacy of another party.
-
E.
hasPartiesDescription
Indicates that a relationship or event includes a textual description of the parties involved.
- 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_69a4934d9930819099eed80096b0597d |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a64adf2c81908e48090be35dd9d9 |
completed | March 1, 2026, 8:49 p.m. |
| PD | Predicate disambiguation | batch_69a4a4fc734c81908fbd36386d5746d6 |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:37 p.m.