Triple
T15229197
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Albert |
E363953
|
entity |
| Predicate | eventDuringWorldWarI |
P43732
|
FINISHED |
| Object | heavily damaged in World War I |
—
|
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: heavily damaged in World War I | Statement: [Albert, eventDuringWorldWarI, heavily damaged in World War I]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eventDuringWorldWarI Context triple: [Albert, eventDuringWorldWarI, heavily damaged in World War I]
-
A.
positionOnWorldWarI
Indicates a person’s or group’s stance, opinion, or policy regarding World War I.
-
B.
worldWarIIService
Indicates that an entity served in some capacity during World War II.
-
C.
roleInWorldWarI
chosen
Indicates the specific function, position, or involvement an entity had during World War I.
-
D.
worldWarITheater
Indicates that the subject is a theater, front, or region in which military operations of World War I took place.
-
E.
duringWorldWar
Indicates that one entity’s action, state, or relationship occurred within the temporal span of World War II.
- 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_69d85a0ce24c81909c4d3b6475548c95 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0078ccdf48190b34eabd9e24e45a1 |
completed | April 15, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69deca899d5c8190be4a7c71e1683c69 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:12 a.m.