Triple
T19281102
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Messier 19 |
E482188
|
entity |
| Predicate | isHighlyElongated |
P71793
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Messier 19, isHighlyElongated, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isHighlyElongated Context triple: [Messier 19, isHighlyElongated, true]
-
A.
isElongatedDueTo
Indicates that one entity becomes longer in shape, form, or duration specifically as a result of the influence or effect of another entity or factor.
-
B.
hasLongStretchIn
chosen
Indicates that something extends for a considerable or continuous distance within a specified area, medium, or context.
-
C.
isEccentric
Indicates that an entity behaves or appears in a way that deviates noticeably from conventional or expected norms.
-
D.
isStretchOf
Indicates that one linear feature (such as a road, river, or path) constitutes a continuous segment or portion of another, longer linear feature.
-
E.
hasUnusualMorphology
Indicates that an entity possesses structural or anatomical features that deviate significantly from what is typical or expected for its kind.
- 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_69d8e8cf61b0819096fe3e4107827c4e |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fbff1e6c819094ae6a5ad40adb65 |
completed | April 20, 2026, 10:12 a.m. |
| PD | Predicate disambiguation | batch_69e4dd07a7208190afcd51ba1dc87c33 |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:30 p.m.