Triple
T18541214
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Messier 82 |
E453102
|
entity |
| Predicate | centralRegionDominatedBy |
P132077
|
FINISHED |
| Object | intense star formation |
—
|
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: intense star formation | Statement: [Messier 82, centralRegionDominatedBy, intense star formation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: centralRegionDominatedBy Context triple: [Messier 82, centralRegionDominatedBy, intense star formation]
-
A.
dominatedRegion
Indicates that one entity exercises controlling power or authority over a particular geographic or conceptual region.
-
B.
dominantRegion
Indicates that one region exerts primary control, influence, or prominence over another region within a given context.
-
C.
dominanceRegion
Indicates that one entity exerts primary control, influence, or priority over a defined area, range, or scope relative to others.
-
D.
coreRegionOf
Indicates that one entity constitutes the central or most essential part of another entity’s structure, area, or domain.
-
E.
occupiedRegion
Indicates that an entity has taken control of and is currently holding a specific geographic area or region.
- 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_69d8d387b5548190aa030dad2cb4947e |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e534b749b88190ad03b26bee3c89df |
completed | April 19, 2026, 8:01 p.m. |
| PD | Predicate disambiguation | batch_69e469e274a48190a570b25cfef4d890 |
completed | April 19, 2026, 5:36 a.m. |
| PDg | Predicate description generation | batch_69e46d2b93bc8190a6070018d7046547 |
completed | April 19, 2026, 5:50 a.m. |
Created at: April 10, 2026, 11:37 a.m.