Triple
T7391013
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | History of the Latin and Teutonic Nations 1494–1514 |
E170495
|
entity |
| Predicate | coversEventType |
P56248
|
FINISHED |
| Object | international relations |
—
|
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 relations | Statement: [History of the Latin and Teutonic Nations 1494–1514, coversEventType, international relations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coversEventType Context triple: [History of the Latin and Teutonic Nations 1494–1514, coversEventType, international relations]
-
A.
coversEvent
Indicates that one event includes, spans, or encompasses the time period or occurrence of another event.
-
B.
hasEventType
Indicates that an event is associated with, or classified under, a specific type or category of event.
-
C.
coversActionType
chosen
Indicates that one entity’s scope, responsibility, or applicability includes or encompasses a particular type of action.
-
D.
includesEvents
Indicates that one entity contains or encompasses one or more events as part of its scope or composition.
-
E.
associatedEventType
Indicates that one entity is linked to another by the type or category of event with which it is associated.
- 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_69c68a5e2c9081909e713ce866e0060a |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f2216a5c8190a933b24fda4530d8 |
completed | March 27, 2026, 9:09 p.m. |
| PD | Predicate disambiguation | batch_69c6f0309cc88190b55d278969400294 |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:09 p.m.