Triple
T7433570
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NATO: The First Five Years |
E171550
|
entity |
| Predicate | describesEventType |
P14526
|
FINISHED |
| Object | formation of military alliance |
—
|
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: formation of military alliance | Statement: [NATO: The First Five Years, describesEventType, formation of military alliance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: describesEventType Context triple: [NATO: The First Five Years, describesEventType, formation of military alliance]
-
A.
servesEventType
Indicates that an entity provides or supports a particular type or category of event.
-
B.
eventDescription
Indicates that a textual summary or explanation is provided describing what happens in the event.
-
C.
typeOfEventForStart
Indicates the specific kind or category of event that marks the beginning of something.
-
D.
hasEventType
chosen
Indicates that an event is associated with, or classified under, a specific type or category of event.
-
E.
premiereEventType
Indicates the specific kind of event at which something (such as a work, show, or product) is first publicly presented or launched.
- 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_69c68a63491881909281f73d4d5643bf |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f327480481909c4691fd3333e2ae |
completed | March 27, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69c6f038582c8190bac77c9b5a34b862 |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:12 p.m.