Triple
T20327454
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Caldwell 106 |
E492376
|
entity |
| Predicate | hasCoreDensity |
P61029
|
FINISHED |
| Object | high |
—
|
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: high | Statement: [Caldwell 106, hasCoreDensity, high]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCoreDensity Context triple: [Caldwell 106, hasCoreDensity, high]
-
A.
hasCentralDensity
chosen
Indicates that an entity possesses a specified value for its density at the central or core region.
-
B.
hasMeanDensity
Indicates that one entity possesses a specified average mass per unit volume (mean density).
-
C.
hasCore
Indicates that one entity possesses, contains, or is built around a central or most essential component represented by another entity.
-
D.
hasCorePopulation
Indicates that an entity possesses a central or primary group of individuals that constitute its main population.
-
E.
hasCoreArea
Indicates that an entity possesses a primary or central area that is fundamental to its structure, function, or focus.
- 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_69e0b4a0134081909113563e1c3ba68a |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e677e513608190b70527cd9f4d5da3 |
completed | April 20, 2026, 7 p.m. |
| PD | Predicate disambiguation | batch_69e5762655ac8190a8cc48a29fa2c0c4 |
completed | April 20, 2026, 12:41 a.m. |
Created at: April 16, 2026, 11:21 a.m.