Triple
T25908160
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Undicesima battaglia dell'Isonzo |
E652812
|
entity |
| Predicate | numeroNellaSerie |
P76763
|
FINISHED |
| Object | 11 |
—
|
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: 11 | Statement: [Undicesima battaglia dell'Isonzo, numeroNellaSerie, 11]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numeroNellaSerie Context triple: [Undicesima battaglia dell'Isonzo, numeroNellaSerie, 11]
-
A.
number
Indicates that one entity is associated with a specific numerical value or count in relation to another entity or context.
-
B.
ordinalNumber
Indicates the position or rank of an entity within an ordered sequence (e.g., first, second, third).
-
C.
laterNumber
Indicates that one number occurs or is positioned later than another in a specified ordering or sequence.
-
D.
imoNumber
Indicates that an entity is associated with a specific International Maritime Organization (IMO) identification number used to uniquely identify ships and certain maritime structures.
-
E.
hasPartOfSeriesPosition
chosen
Indicates that an entity occupies a specific position or order within a larger series or sequence.
- 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_69e7ab3d3f8481909bc53ed64c06af33 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f603c15b348190a7f00745b6475b28 |
completed | May 2, 2026, 2:01 p.m. |
| PD | Predicate disambiguation | batch_69f4a0fed15881909b789251fe5d8d45 |
completed | May 1, 2026, 12:47 p.m. |
Created at: April 22, 2026, 8:27 a.m.