Triple
T28735246
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | England |
E730779
|
entity |
| Predicate | unionFormedWith |
P165554
|
FINISHED |
| Object | Scotland |
—
|
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: Scotland | Statement: [England, unionFormedWith, Scotland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: unionFormedWith Context triple: [England, unionFormedWith, Scotland]
-
A.
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.
-
B.
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.
-
C.
union
Indicates that two or more sets are combined into a single set containing all elements that belong to at least one of them.
-
D.
unionForces
Indicates that multiple forces are combined into a single, unified force acting together.
-
E.
unionGoal
Indicates that the entities share a common objective or outcome they aim to achieve together as a unified group.
- F. None of above. chosen
Provenance (4 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_69f6596b210481908af6cd555748f75b |
completed | May 2, 2026, 8:07 p.m. |
| PD | Predicate disambiguation | batch_69f65760fd3081908ffe014a5e2bf069 |
completed | May 2, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69f658ebeca4819096beb3f98f73fe31 |
completed | May 2, 2026, 8:05 p.m. |
Created at: April 28, 2026, 6 a.m.