Triple
T3446668
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canton of Le Mont-Blanc |
E72694
|
entity |
| Predicate | temporalQualification |
P29111
|
FINISHED |
| Object | short-lived |
—
|
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: short-lived | Statement: [Canton of Le Mont-Blanc, temporalQualification, short-lived]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: temporalQualification Context triple: [Canton of Le Mont-Blanc, temporalQualification, short-lived]
-
A.
temporalAspect
chosen
Indicates the time-related characteristics or phase (such as duration, frequency, or temporal status) associated with an event or relationship.
-
B.
temporalRelation
Indicates a relationship that specifies how two events or states are positioned relative to each other in time (e.g., before, after, or overlapping).
-
C.
hasTemporalLocation
Indicates that something occurs, exists, or is valid during a specific time or time interval.
-
D.
temporalEffect
Indicates a relationship where one event, state, or action produces consequences or changes that occur at a later time.
-
E.
hasTemporalJurisdictionFrom
Indicates that an authority’s jurisdiction or control over something begins at a specified 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_69ad85b05c848190b7a28ceec2bd7b74 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adba6efb188190b989fa4d6f28e16b |
completed | March 8, 2026, 6:05 p.m. |
| PD | Predicate disambiguation | batch_69adae0255b48190a9069f7871c7a012 |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:16 p.m.