Triple
T4617806
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Open cluster M25 |
E100907
|
entity |
| Predicate | hasTrumplerClassification |
P25488
|
FINISHED |
| Object | II,3,m |
—
|
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: II,3,m | Statement: [Open cluster M25, hasTrumplerClassification, II,3,m]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTrumplerClassification Context triple: [Open cluster M25, hasTrumplerClassification, II,3,m]
-
A.
areClassifiedBy
chosen
Indicates that entities are assigned to one or more categories, types, or classes according to a specified classification scheme.
-
B.
hasPrincipalTrumpet
Indicates that one entity serves as the principal (lead) trumpet player for another entity, such as an orchestra or ensemble.
-
C.
isClassifiedUnder
Indicates that one entity is categorized or grouped within a broader class, type, or category represented by another entity.
-
D.
isSometimesClassifiedAs
Indicates that an entity is occasionally, but not consistently or universally, categorized under a particular type or class.
-
E.
hasPerformerCharacteristic
Indicates that a performer possesses a particular attribute, quality, or characteristic.
- 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_69bd43cf363c819087fd5ab441b4a3f4 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd59e247448190ad92f194cb1127c5 |
completed | March 20, 2026, 2:29 p.m. |
| PD | Predicate disambiguation | batch_69bd522fd5c48190ad2bffc0a5bc9061 |
completed | March 20, 2026, 1:57 p.m. |
Created at: March 20, 2026, 1:12 p.m.