Triple
T18776010
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NGC 6664 |
E459134
|
entity |
| Predicate | objectClass |
P102949
|
FINISHED |
| Object | open cluster of the Milky Way |
—
|
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: open cluster of the Milky Way | Statement: [NGC 6664, objectClass, open cluster of the Milky Way]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: objectClass Context triple: [NGC 6664, objectClass, open cluster of the Milky Way]
-
A.
typicalObjectType
Indicates that something is a common or characteristic type of object typically associated with or involved in another entity or situation.
-
B.
operatorClass
Indicates the classification or category of an operator in terms of its type, role, or functional group within a system or domain.
-
C.
nodeClass
chosen
Indicates that an entity belongs to, or is categorized as, a particular class or type of node within a graph or network structure.
-
D.
notableObject
Indicates that an entity is especially significant, famous, or noteworthy as an object in a given context or domain.
-
E.
objet
Indicates that one entity is the object (recipient or target) of an action or relation performed by another entity.
- 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_69d8d395dba0819087568404508590cb |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5933ad4288190b17e5fad57d8417d |
completed | April 20, 2026, 2:45 a.m. |
| PD | Predicate disambiguation | batch_69e48d1126e4819099607837ed5aadca |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:52 a.m.