Triple
T17682044
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Italian battleship Conte di Cavour |
E440792
|
entity |
| Predicate | statusAfterTaranto |
P128554
|
FINISHED |
| Object | raised and placed in drydock for repairs |
—
|
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: raised and placed in drydock for repairs | Statement: [Italian battleship Conte di Cavour, statusAfterTaranto, raised and placed in drydock for repairs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusAfterTaranto Context triple: [Italian battleship Conte di Cavour, statusAfterTaranto, raised and placed in drydock for repairs]
-
A.
statusAfterCunaxa
Indicates the status or condition of an entity following the events of the Battle of Cunaxa.
-
B.
statusAfter1806
Indicates the status or condition of an entity specifically in the period following the year 1806.
-
C.
statusAfter1627
Indicates the condition or state of an entity as it exists after the year 1627.
-
D.
statusAfter1569
Indicates the status or condition an entity has after the year 1569, typically contrasting it with its prior status.
-
E.
statusAfterRescue
Indicates the condition or state an entity is in following a rescue event or operation.
- 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_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. |
| PDg | Predicate description generation | batch_69e3cfaac2b881909e1140339eb1a0dd |
completed | April 18, 2026, 6:38 p.m. |
Created at: April 10, 2026, 10:02 a.m.