Triple
T21593
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | International Monetary Fund headquarters |
E428
|
entity |
| Predicate | securityLevel |
P406
|
FINISHED |
| Object | high |
—
|
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: high | Statement: [International Monetary Fund headquarters, securityLevel, high]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: securityLevel Context triple: [International Monetary Fund headquarters, securityLevel, high]
-
A.
securityClassification
chosen
Indicates the level or category of security sensitivity or access restriction assigned to an entity.
-
B.
security
Indicates that an entity provides protection, safety measures, or safeguards to another entity or against specific threats or risks.
-
C.
protectedBy
Indicates that one entity provides protection, defense, or safeguarding for another entity.
-
D.
honorLevel
Indicates the degree or status of respect, distinction, or recognition accorded to an entity relative to others.
-
E.
protects
Indicates taking action to keep someone or something safe from harm, danger, or negative effects.
- 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_69a243b4ac2c8190b93c303df797b7b2 |
completed | Feb. 28, 2026, 1:24 a.m. |
| NER | Named-entity recognition | batch_69a246e94ca881908f7a7d2c0b293033 |
completed | Feb. 28, 2026, 1:37 a.m. |
| PD | Predicate disambiguation | batch_69a24654724481909ba14b7f68d2a472 |
completed | Feb. 28, 2026, 1:35 a.m. |
Created at: Feb. 28, 2026, 1:34 a.m.