Triple
T21026263
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M49 |
E517948
|
entity |
| Predicate | dominatesRegionOf |
P80160
|
FINISHED |
| Object | southern Virgo Cluster |
—
|
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: southern Virgo Cluster | Statement: [M49, dominatesRegionOf, southern Virgo Cluster]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dominatesRegionOf Context triple: [M49, dominatesRegionOf, southern Virgo Cluster]
-
A.
dominatedRegion
Indicates that one entity exercises controlling power or authority over a particular geographic or conceptual region.
-
B.
dominanceRegion
chosen
Indicates that one entity exerts primary control, influence, or priority over a defined area, range, or scope relative to others.
-
C.
dominantRegion
Indicates that one region exerts primary control, influence, or prominence over another region within a given context.
-
D.
centralRegionDominatedBy
Indicates that the central region of one entity is controlled, influenced, or overwhelmingly characterized by another entity.
-
E.
isRegionOf
Indicates that one entity is a geographic or administrative region belonging to, contained within, or associated with another entity.
- 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_69e0b503275c8190afd9a163f997c709 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6fc7c262c8190bceb8fd26be76983 |
completed | April 21, 2026, 4:26 a.m. |
| PD | Predicate disambiguation | batch_69e5dbf274ac81909bbf245627dc8fdc |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 1:55 p.m.