Triple
T19730184
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Messier 4 |
E473829
|
entity |
| Predicate | hasCentralBarStructure |
P137112
|
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: [Messier 4, hasCentralBarStructure, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCentralBarStructure Context triple: [Messier 4, hasCentralBarStructure, yes]
-
A.
hasCentralSection
Indicates that an entity possesses a distinct middle or central part within its overall structure or composition.
-
B.
hasCentralFigure
Indicates that something features a primary or most important figure at its core or focus.
-
C.
hasBars
Indicates that one entity possesses, contains, or is equipped with bars as a defining feature or component.
-
D.
hasCentralAxis
Indicates that one entity serves as the primary central axis or line of symmetry around which another entity is organized, aligned, or structured.
-
E.
barStructure
Indicates that one entity serves as the structural framework or supporting construction for a bar (such as a counter, pub, or similar establishment).
- 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_69d8e517ebd48190979ee76723bcfadf |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e649fbeaf081909e9356229eaf84dd |
completed | April 20, 2026, 3:45 p.m. |
| PD | Predicate disambiguation | batch_69e5304a7aac8190ac13f75f0c008e45 |
completed | April 19, 2026, 7:43 p.m. |
| PDg | Predicate description generation | batch_69e532bbedf081908d801600e2af94a7 |
completed | April 19, 2026, 7:53 p.m. |
Created at: April 10, 2026, 1:47 p.m.