Triple
T19261543
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abell 3526 |
E481659
|
entity |
| Predicate | showsMergerActivity |
P135129
|
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: [Abell 3526, showsMergerActivity, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: showsMergerActivity Context triple: [Abell 3526, showsMergerActivity, yes]
-
A.
hasMerger
Indicates a relationship where two or more entities combine into a single entity through a merger event.
-
B.
showsThat
Indicates that one entity demonstrates, proves, or provides evidence for the truth or validity of another.
-
C.
mergerResult
Indicates that one or more entities have combined into a single entity, specifying the outcome or resulting entity of the merger.
-
D.
mergerImplemented
Indicates that a planned merger between entities has been fully executed and put into effect.
-
E.
mergerType
Indicates the specific kind or category of merger relationship that exists between the involved entities.
- 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_69d8e8ce54cc8190998418ff1f66ef28 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fb8a022c8190b313e9d11d38e482 |
completed | April 20, 2026, 10:10 a.m. |
| PD | Predicate disambiguation | batch_69e4dd002d00819088b625056edfb74e |
completed | April 19, 2026, 1:47 p.m. |
| PDg | Predicate description generation | batch_69e4ddcf50108190a09d0f1291c17374 |
completed | April 19, 2026, 1:51 p.m. |
Created at: April 10, 2026, 1:28 p.m.