Triple
T4099
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Atlantic Treaty |
E77
|
entity |
| Predicate | subjectMatter |
P450
|
FINISHED |
| Object | security and defense |
—
|
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: security and defense | Statement: [North Atlantic Treaty, subjectMatter, security and defense]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subjectMatter Context triple: [North Atlantic Treaty, subjectMatter, security and defense]
-
A.
category
Indicates that one entity is classified as a member or type within the grouping or class defined by another entity.
-
B.
fieldOfWork
Indicates the professional or academic domain in which an entity is primarily engaged or specializes.
-
C.
sector
Indicates that an entity operates in, belongs to, or is associated with a particular economic or industrial sector.
-
D.
theme
Indicates the entity that is the primary participant or content affected or characterized by an action, event, or state.
-
E.
submittedTo
Indicates that one entity has formally sent or presented something (such as a document, request, or work) to another entity for consideration, review, or processing.
- 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_69a238d6b47881909e68288aed2fd858 |
completed | Feb. 28, 2026, 12:37 a.m. |
| NER | Named-entity recognition | batch_69a23bcc8eb48190b897cc331563980a |
completed | Feb. 28, 2026, 12:50 a.m. |
| PD | Predicate disambiguation | batch_69a23994309081909ff3e869deef2156 |
completed | Feb. 28, 2026, 12:40 a.m. |
| PDg | Predicate description generation | batch_69a23bcb4bbc819093775f623998d62d |
completed | Feb. 28, 2026, 12:50 a.m. |
Created at: Feb. 28, 2026, 12:40 a.m.