Triple
T17682037
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Italian battleship Conte di Cavour |
E440792
|
entity |
| Predicate | dateOfNotableEngagement |
P49061
|
FINISHED |
| Object | 9 July 1940 |
—
|
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: 9 July 1940 | Statement: [Italian battleship Conte di Cavour, dateOfNotableEngagement, 9 July 1940]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateOfNotableEngagement Context triple: [Italian battleship Conte di Cavour, dateOfNotableEngagement, 9 July 1940]
-
A.
engagementDate
Indicates the date on which two entities formally become engaged or committed to a relationship or agreement.
-
B.
notableEngagement
Indicates a significant interaction, involvement, or participation between entities that is noteworthy or distinguished in some context.
-
C.
lastRegularAppearanceDate
Indicates the date on which an entity made its most recent standard or non-special appearance.
-
D.
notableOperationDate
chosen
Indicates the date on which a significant or noteworthy operation, event, or activity associated with an entity took place.
-
E.
lastSpeechDate
Indicates the date on which an entity most recently gave or delivered a speech.
- 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_69d8b9e940b081908b862bb0e6e89b0d |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e4704514d481908aad4172fa930e6b |
completed | April 19, 2026, 6:03 a.m. |
| PD | Predicate disambiguation | batch_69e3cde3673c8190a889e14ba1f07dc1 |
completed | April 18, 2026, 6:30 p.m. |
Created at: April 10, 2026, 10:02 a.m.