Triple
T18842278
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NGC 2024 |
E460825
|
entity |
| Predicate | ageOfEmbeddedCluster |
P133136
|
FINISHED |
| Object | ~200,000 years |
—
|
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: ~200,000 years | Statement: [NGC 2024, ageOfEmbeddedCluster, ~200,000 years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ageOfEmbeddedCluster Context triple: [NGC 2024, ageOfEmbeddedCluster, ~200,000 years]
-
A.
isOldCluster
Indicates that a given cluster has existed for a long time or has reached an advanced age relative to other clusters.
-
B.
hasCluster
Indicates that one entity possesses, contains, or is associated with a specific cluster or grouping of related elements.
-
C.
typeOfCluster
Indicates that one entity is classified as a specific kind or category of cluster in relation to another entity.
-
D.
associatedWithCluster
Indicates that an entity is linked or grouped with a particular cluster, typically sharing common characteristics or membership within that cluster.
-
E.
isClusteredFormation
Indicates that multiple entities are arranged or grouped closely together in a compact formation.
- 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_69d8dcfa11e4819090ab1ef5bdcd2b2e |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5b8eb32548190b2313e877f6ff179 |
completed | April 20, 2026, 5:26 a.m. |
| PD | Predicate disambiguation | batch_69e48d1e7dac81909ea1e758c87773c5 |
completed | April 19, 2026, 8:06 a.m. |
| PDg | Predicate description generation | batch_69e49785fd7081909577e90a55df0a35 |
completed | April 19, 2026, 8:51 a.m. |
Created at: April 10, 2026, 11:56 a.m.