Triple
T31190355
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SMS Novara |
E795160
|
entity |
| Predicate | yearOfNotableEngagement |
P104850
|
FINISHED |
| Object | 1917 |
—
|
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: 1917 | Statement: [SMS Novara, yearOfNotableEngagement, 1917]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: yearOfNotableEngagement Context triple: [SMS Novara, yearOfNotableEngagement, 1917]
-
A.
firstEngagementYear
Indicates the calendar year in which an entity first became engaged in a specified relationship, activity, or involvement.
-
B.
notableEngagement
Indicates a significant interaction, involvement, or participation between entities that is noteworthy or distinguished in some context.
-
C.
activeInYear
Indicates that an entity was active, functioning, or operational during a specified year.
-
D.
notableProjectYear
chosen
Indicates the year in which a notable project associated with an entity took place, was created, or was prominently recognized.
-
E.
yearOfMeeting
Indicates the specific calendar year in which the meeting between the referenced entities took place.
- 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_69f224d7a6a481908187c4362a8a525f |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fce7671f108190bf3ebf54339068b5 |
completed | May 7, 2026, 7:26 p.m. |
| PD | Predicate disambiguation | batch_69fce5b5a84c81908ac1b5b9f08d48d0 |
completed | May 7, 2026, 7:19 p.m. |
Created at: April 29, 2026, 9:08 p.m.