Triple
T24437905
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A Chronicle of the Thirty Years' War |
E616173
|
entity |
| Predicate | indicatesStructure |
P156130
|
FINISHED |
| Object | seriesOfEpisodes |
—
|
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: seriesOfEpisodes | Statement: [A Chronicle of the Thirty Years' War, indicatesStructure, seriesOfEpisodes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: indicatesStructure Context triple: [A Chronicle of the Thirty Years' War, indicatesStructure, seriesOfEpisodes]
-
A.
definesStructure
Indicates that one entity specifies or determines the organizational form, composition, or arrangement of another entity.
-
B.
haveStructure
Indicates that an entity possesses a particular internal organization, arrangement, or structural composition.
-
C.
supportsStructure
Indicates that one entity bears or provides physical support to another entity, helping to hold it up or maintain its structural stability.
-
D.
encodingStructure
Indicates the structural scheme or format used to encode information or data.
-
E.
hasStructureType
Indicates that an entity possesses or is classified by a specific structural type or configuration.
- 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_69e2d7ec44b081909ccaf1f3bbec0641 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f297881fa08190b82bdc5ebeae96f7 |
completed | April 29, 2026, 11:43 p.m. |
| PD | Predicate disambiguation | batch_69f287d3237c819099559c00f83131d8 |
completed | April 29, 2026, 10:36 p.m. |
| PDg | Predicate description generation | batch_69f28f4d978c81908310c01def2514cc |
completed | April 29, 2026, 11:07 p.m. |
Created at: April 18, 2026, 2:16 a.m.