Triple
T16597795
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Technical Secretariat |
E403252
|
entity |
| Predicate | canExistAtLevel |
P51053
|
FINISHED |
| Object | international organization |
—
|
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 organization | Statement: [Technical Secretariat, canExistAtLevel, international organization]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canExistAtLevel Context triple: [Technical Secretariat, canExistAtLevel, international organization]
-
A.
canExistAt
chosen
Indicates that an entity is capable of being present or occurring at a specified location, time, or context.
-
B.
meetsAtLevel
Indicates that two or more entities encounter or interact with each other at a specific hierarchical, structural, or progression level.
-
C.
hasLevel
Indicates that an entity possesses or is associated with a particular degree, rank, or stage within an ordered scale or hierarchy.
-
D.
hasDataAtLevel
Indicates that an entity possesses or is associated with data corresponding to a specific level or tier.
-
E.
containsLevel
Indicates that one entity includes or encompasses a specific level or layer within its structure or hierarchy.
- 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_69d883880d0c81908b5fcd454e767b60 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e35d7367308190bf57b4a6a7bd33cc |
completed | April 18, 2026, 10:31 a.m. |
| PD | Predicate disambiguation | batch_69e296a7d9d0819088555bca6c936e79 |
completed | April 17, 2026, 8:23 p.m. |
Created at: April 10, 2026, 5:16 a.m.