Triple
T2896707
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Act anent Peace and War 1703 |
E63956
|
entity |
| Predicate | temporalProximity |
P4137
|
FINISHED |
| Object | enacted four years before the Union of 1707 |
—
|
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: enacted four years before the Union of 1707 | Statement: [Act anent Peace and War 1703, temporalProximity, enacted four years before the Union of 1707]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: temporalProximity Context triple: [Act anent Peace and War 1703, temporalProximity, enacted four years before the Union of 1707]
-
A.
temporalRelation
chosen
Indicates a relationship that specifies how two events or states are positioned relative to each other in time (e.g., before, after, or overlapping).
-
B.
closerTo
Indicates that one entity is at a smaller distance to a reference entity than another entity is.
-
C.
temporalAspect
Indicates the time-related characteristics or phase (such as duration, frequency, or temporal status) associated with an event or relationship.
-
D.
occursNear
Indicates that one event or entity takes place or exists in close spatial proximity to another.
-
E.
hasTemporalLocation
Indicates that something occurs, exists, or is valid during a specific time or time interval.
- 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_69ab4c45822c8190830c5f2bb97bcfd0 |
completed | March 6, 2026, 9:51 p.m. |
| NER | Named-entity recognition | batch_69abe08e7b248190a6bb0f6999f99c23 |
completed | March 7, 2026, 8:23 a.m. |
| PD | Predicate disambiguation | batch_69abdd17bcdc8190aa47274a50ba4ad4 |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 10:08 p.m.