Triple
T29768499
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trumpler II 3 m |
E753981
|
entity |
| Predicate | richnessDescription |
P141746
|
FINISHED |
| Object | moderately rich |
—
|
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: moderately rich | Statement: [Trumpler II 3 m, richnessDescription, moderately rich]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: richnessDescription Context triple: [Trumpler II 3 m, richnessDescription, moderately rich]
-
A.
richness
Indicates that an entity possesses a high degree of abundance, complexity, or density in some valued attribute or resource.
-
B.
hasRichnessClass
chosen
Indicates that an entity is assigned to a particular richness category or level within a defined classification system.
-
C.
enrichmentPlantRevealed
Indicates that the location or existence of a nuclear enrichment plant has been disclosed or made known.
-
D.
richIn
Indicates that something contains a high amount or concentration of a particular substance, quality, or resource.
-
E.
shareBiodiversityFeature
Indicates that two or more entities have a biodiversity-related characteristic, attribute, or feature in common.
- 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_69f0ef827ff88190ade56e0b0846b713 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f6745f8354819085a81de5c32dd49e |
completed | May 2, 2026, 10:02 p.m. |
| PD | Predicate disambiguation | batch_69f66ac1a4fc81909740d2e52fbe6970 |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 28, 2026, 8:40 p.m.