Triple
T2868802
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parlamaid na h-Alba |
E63506
|
entity |
| Predicate | canBeDissolvedEarly |
P42838
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Parlamaid na h-Alba, canBeDissolvedEarly, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeDissolvedEarly Context triple: [Parlamaid na h-Alba, canBeDissolvedEarly, yes]
-
A.
canBeDissolvedWith
Indicates that one entity is capable of being dissolved or broken down when exposed to another specified substance or medium.
-
B.
canBeHeldEarly
Indicates that an event, action, or process is allowed to occur earlier than its originally scheduled or typical time.
-
C.
wasDissolvedAfter
Indicates that one entity ceased to exist or operate at a later point in time than another entity’s dissolution.
-
D.
dissolvedDueTo
Indicates that a relationship, agreement, or entity came to an end as a result of a specified cause or event.
-
E.
dissolutionTime
Indicates the point in time at which a relationship, structure, or entity ceases to exist or is formally terminated.
- 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_69ab4c42fb8c8190b36e161d47c03b81 |
completed | March 6, 2026, 9:50 p.m. |
| NER | Named-entity recognition | batch_69abdfdfef1881909dc52a1b34cd24e3 |
completed | March 7, 2026, 8:20 a.m. |
| PD | Predicate disambiguation | batch_69abdd123ec48190af50a1859aea50b7 |
completed | March 7, 2026, 8:08 a.m. |
| PDg | Predicate description generation | batch_69abddedd72c819094a9c4161af07780 |
completed | March 7, 2026, 8:12 a.m. |
Created at: March 6, 2026, 10:02 p.m.