Triple
T25882870
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bellavista Fortress |
E652098
|
entity |
| Predicate | roleInMemory |
P87295
|
FINISHED |
| Object | site of memory of the 1948 civil war |
—
|
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: site of memory of the 1948 civil war | Statement: [Bellavista Fortress, roleInMemory, site of memory of the 1948 civil war]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInMemory Context triple: [Bellavista Fortress, roleInMemory, site of memory of the 1948 civil war]
-
A.
memoryRole
chosen
Indicates the specific function or responsibility an entity has in relation to storing, retaining, or managing information or experiences.
-
B.
roleInRepertoire
Indicates that an entity serves a specific role or function within a larger repertoire, collection, or set of items.
-
C.
roleOn
Indicates that an entity holds or performs a specific role or function within another entity, context, or activity.
-
D.
roleInName
Indicates that a specific role, title, or position is included as part of an entity’s name or naming expression.
-
E.
roleInOperation
Indicates that an entity holds a specific function, duty, or position within a particular operation or activity.
- 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_69e7ab3b92cc81908febd90317862647 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f727afd5d88190ad48735cd1b32787 |
completed | May 3, 2026, 10:47 a.m. |
| PD | Predicate disambiguation | batch_69f72737c42c8190a3f781a5e98868ff |
completed | May 3, 2026, 10:45 a.m. |
Created at: April 22, 2026, 8:17 a.m.