Triple
T19261674
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NGC 6712 |
E481662
|
entity |
| Predicate | colorExcess |
P57002
|
FINISHED |
| Object | heavily reddened |
—
|
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: heavily reddened | Statement: [NGC 6712, colorExcess, heavily reddened]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: colorExcess Context triple: [NGC 6712, colorExcess, heavily reddened]
-
A.
hasColorExcess
chosen
Indicates that an entity exhibits a measured amount of color excess, typically representing the difference between its observed color and its intrinsic or expected color.
-
B.
colorCharge
Indicates a relationship where an entity possesses a specific quantum color charge (such as red, green, or blue) in the context of strong nuclear interactions.
-
C.
colors
Indicates that one entity assigns, describes, or provides the color or colors of another entity.
-
D.
crestColor
Indicates the color characteristic of an entity’s crest.
-
E.
colorTincture
Indicates that one entity has a specific heraldic color or tincture applied to it.
- 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_69d8e8ce54cc8190998418ff1f66ef28 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fb8a022c8190b313e9d11d38e482 |
completed | April 20, 2026, 10:10 a.m. |
| PD | Predicate disambiguation | batch_69e4dd07a7208190afcd51ba1dc87c33 |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:28 p.m.