Triple
T35896726
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monte Ceneri |
E1038243
|
entity |
| Predicate | hasStrategicRoleSince |
P118083
|
FINISHED |
| Object | historical times |
—
|
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: historical times | Statement: [Monte Ceneri, hasStrategicRoleSince, historical times]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStrategicRoleSince Context triple: [Monte Ceneri, hasStrategicRoleSince, historical times]
-
A.
hasLeadershipRoleSince
Indicates that an entity has held a leadership role starting from a specified point in time and continuing from that date onward.
-
B.
hasHistoricalRoleAs
Indicates that an entity has served in a specific historical capacity, function, or position during a particular period or context.
-
C.
hasStrategicFunction
Indicates that an entity serves a planned, goal-oriented role or purpose within a broader strategy or system.
-
D.
strategicSince
chosen
Indicates that a relationship, status, or condition has been considered strategic starting from a specific point in time.
-
E.
hasOppositionRoleSince
Indicates that an entity has held a specific opposition role or position continuously since a given point in time.
- 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_69f76e2190f88190beb2eed798a4ef01 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a001cc0ff588190bb7c8a6fd427d02b |
completed | May 10, 2026, 5:50 a.m. |
| PD | Predicate disambiguation | batch_6a001b3ea18c8190aeda7a32b2697490 |
completed | May 10, 2026, 5:44 a.m. |
Created at: May 3, 2026, 4:06 p.m.