Triple
T5075166
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Messier 55 |
E114375
|
entity |
| Predicate | coreCollapseStatus |
P61267
|
FINISHED |
| Object | non–core-collapsed |
—
|
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: non–core-collapsed | Statement: [Messier 55, coreCollapseStatus, non–core-collapsed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coreCollapseStatus Context triple: [Messier 55, coreCollapseStatus, non–core-collapsed]
-
A.
collapsedWith
Indicates that one entity fell down or caved in together with another entity, typically as part of the same collapse event.
-
B.
collapsedDuring
Indicates that one entity structurally failed or fell down while another specified event or process was occurring.
-
C.
collapsedOn
Indicates that one entity physically fell or caved in onto another entity, ending up resting on or covering it.
-
D.
collapsedAfter
Indicates that one entity collapsed at some point in time after another specified event or entity’s collapse.
-
E.
expansionStatus
Indicates the current state or phase of growth, enlargement, or extension of something relative to its previous or intended size or scope.
- 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_69bd443cf28c8190ad371d603563dbdd |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd74d2243481908c1ae62f7123c4e9 |
completed | March 20, 2026, 4:24 p.m. |
| PD | Predicate disambiguation | batch_69bd7157fe608190b4515d56fdd0a616 |
completed | March 20, 2026, 4:10 p.m. |
| PDg | Predicate description generation | batch_69bd73d90b608190bd6c2407e84e2b64 |
completed | March 20, 2026, 4:20 p.m. |
Created at: March 20, 2026, 1:39 p.m.