Triple
T870034
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M45 |
E18788
|
entity |
| Predicate | typeOfCluster |
P20411
|
FINISHED |
| Object | young open cluster |
—
|
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: young open cluster | Statement: [M45, typeOfCluster, young open cluster]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfCluster Context triple: [M45, typeOfCluster, young open cluster]
-
A.
deploymentType
Indicates the manner or configuration in which a system, application, or component is deployed or made operational.
-
B.
acceleratorType
Indicates the kind or category of accelerator associated with or used by an entity.
-
C.
typeOfDivision
Indicates the specific category or kind of division that characterizes how something is separated, organized, or partitioned.
-
D.
hasITCluster
Indicates that an entity possesses, hosts, or is associated with a specific information technology (IT) cluster.
-
E.
nebulaType
Indicates the specific classification or category of a nebula based on its physical and observational characteristics.
- 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_69a4938ce8688190a24bdfef82ba7d21 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ac811e548190a72b7a10b5ea8665 |
completed | March 1, 2026, 9:15 p.m. |
| PD | Predicate disambiguation | batch_69a4aa89ca008190b50d061ac7fe19f9 |
completed | March 1, 2026, 9:07 p.m. |
| PDg | Predicate description generation | batch_69a4ab498bb0819080e3afb684b504b6 |
completed | March 1, 2026, 9:10 p.m. |
Created at: March 1, 2026, 7:39 p.m.