Triple
T29768512
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trumpler II 3 m |
E753981
|
entity |
| Predicate | appliesToObjectType |
P194703
|
FINISHED |
| Object | Galactic 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: Galactic open cluster | Statement: [Trumpler II 3 m, appliesToObjectType, Galactic open cluster]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliesToObjectType Context triple: [Trumpler II 3 m, appliesToObjectType, Galactic open cluster]
-
A.
appliesTo
Indicates that something is relevant, valid, or has effect in relation to a particular entity, case, or context.
-
B.
appliesToPropertyType
Indicates that something (such as a rule, constraint, or operation) is relevant to or valid for a specific type of property.
-
C.
appliesToResourceType
Indicates that a rule, condition, or operation is specifically targeted at and relevant for a particular type or category of resource.
-
D.
appliedToEntityType
Indicates that something (such as a rule, constraint, or operation) is specifically applied to entities of a given type.
-
E.
appliesToDataType
Indicates that a rule, operation, or construct is specifically intended to be used with, or is valid for, a particular data type.
- 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_69f0ef827ff88190ade56e0b0846b713 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69fd82ed2a4c81908bd7797fbd2e3d08 |
completed | May 8, 2026, 6:30 a.m. |
| PD | Predicate disambiguation | batch_69fd814cc10481908e4f8123d35a5d0c |
completed | May 8, 2026, 6:23 a.m. |
| PDg | Predicate description generation | batch_69fd82ebe1c081908455fc45b6e45178 |
completed | May 8, 2026, 6:30 a.m. |
Created at: April 28, 2026, 8:40 p.m.