Triple
T28735247
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | England |
E730779
|
entity |
| Predicate | unionFormationEvent |
P13846
|
FINISHED |
| Object | Acts of Union 1707 |
—
|
NE NERFINISHED |
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: Acts of Union 1707 | Statement: [England, unionFormationEvent, Acts of Union 1707]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: unionFormationEvent Context triple: [England, unionFormationEvent, Acts of Union 1707]
-
A.
unionFormedWith
Indicates that two or more entities have come together to create a unified group, organization, or alliance.
-
B.
unionEvent
chosen
Indicates an event in which two or more entities are joined or combined into a single unified whole.
-
C.
unionResponse
Indicates that an entity’s action or decision is made as a collective or official response from a union or organized group of workers.
-
D.
unionForm
Indicates that an entity is a form, document, or process used to establish, join, or manage membership in a union or union-related organization.
-
E.
unionForces
Indicates that multiple forces are combined into a single, unified force acting together.
- 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_69f043eae0908190b28ce314686247d7 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f65a6c900881908f18b61273d7bf8d |
completed | May 2, 2026, 8:11 p.m. |
| PD | Predicate disambiguation | batch_69f659ce58408190ba9e007b4810d4d0 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 28, 2026, 6 a.m.