Triple
T4580841
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | University of Wales |
E101848
|
entity |
| Predicate | announcedMerger |
P4650
|
FINISHED |
| Object | 2010 |
—
|
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: 2010 | Statement: [University of Wales, announcedMerger, 2010]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: announcedMerger Context triple: [University of Wales, announcedMerger, 2010]
-
A.
acquisitionAnnouncedBy
Indicates that an acquisition event was publicly announced by the specified announcing entity (such as a company or organization).
-
B.
mergerSettlement
Indicates a legal or financial resolution reached between parties involved in a merger, typically settling disputes or claims arising from the merger transaction.
-
C.
mergerType
Indicates the specific kind or category of merger relationship that exists between the involved entities.
-
D.
mergerPartner
Indicates that two entities are involved as counterparties in a merger transaction with each other.
-
E.
announcedThat
chosen
Indicates that one entity publicly communicated or declared a specific fact, decision, or piece of information about another entity or situation.
- 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_69bd43d4ce208190b53158c882b222e3 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd58e534708190a1ba9c5a29b3774d |
completed | March 20, 2026, 2:25 p.m. |
| PD | Predicate disambiguation | batch_69bd5228b70c8190ac48705e35a710c1 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:10 p.m.