Triple
T22937539
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NGC 5866 Group |
E569626
|
entity |
| Predicate | hasCentralRegionDominatedBy |
P132077
|
FINISHED |
| Object | NGC 5866 |
—
|
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: NGC 5866 | Statement: [NGC 5866 Group, hasCentralRegionDominatedBy, NGC 5866]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCentralRegionDominatedBy Context triple: [NGC 5866 Group, hasCentralRegionDominatedBy, NGC 5866]
-
A.
centralRegionDominatedBy
chosen
Indicates that the central region of one entity is controlled, influenced, or overwhelmingly characterized by another entity.
-
B.
hasCentralRegion
Indicates that an entity possesses or is associated with a primary or central area within its overall structure or domain.
-
C.
dominatedRegion
Indicates that one entity exercises controlling power or authority over a particular geographic or conceptual region.
-
D.
hasRegionCenter
Indicates that a region is associated with a specific central point or location that serves as its geometric or administrative center.
-
E.
isCentralTo
Indicates that something plays a primary, essential, or defining role in relation to something else, such that the latter depends on or is organized around it.
- 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_69e24590862c8190858f180ad302adab |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f18136bf448190afa04f8b55a8bb6e |
completed | April 29, 2026, 3:55 a.m. |
| PD | Predicate disambiguation | batch_69ef3b882e708190b0eb0c87021c75b8 |
completed | April 27, 2026, 10:33 a.m. |
Created at: April 17, 2026, 3:45 p.m.