Triple
T17702235
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Royan |
E441334
|
entity |
| Predicate | statusOfRoyanBeforeBattle |
P73538
|
FINISHED |
| Object | German-held city |
—
|
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: German-held city | Statement: [Battle of Royan, statusOfRoyanBeforeBattle, German-held city]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusOfRoyanBeforeBattle Context triple: [Battle of Royan, statusOfRoyanBeforeBattle, German-held city]
-
A.
statusOfCityBeforeBattle
chosen
Indicates the condition or situation a city was in immediately prior to a specific battle.
-
B.
statusDuringBattle
Indicates the condition or state an entity has while a specific battle or combat event is taking place.
-
C.
preFightStatusOfAli
Indicates the condition or state Ali was in immediately before a fight or combat event.
-
D.
statusBeforeWar
Indicates the condition or situation of an entity as it existed prior to the onset of a specified war.
-
E.
statusAfterBattle
Indicates the condition or state of an entity following the completion of a battle or combat encounter.
- 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_69d8b9ea20b48190ace88bb46b01e6a9 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e4715c3980819094b080a871df1100 |
completed | April 19, 2026, 6:08 a.m. |
| PD | Predicate disambiguation | batch_69e3cde601d4819097903f471f1fe99a |
completed | April 18, 2026, 6:31 p.m. |
Created at: April 10, 2026, 10:05 a.m.