Triple
T22999852
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Melotte 88 |
E572604
|
entity |
| Predicate | hasCoreRadius_pc |
P56975
|
FINISHED |
| Object | about 3 |
—
|
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: about 3 | Statement: [Melotte 88, hasCoreRadius_pc, about 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCoreRadius_pc Context triple: [Melotte 88, hasCoreRadius_pc, about 3]
-
A.
coreRadius_pc
chosen
Indicates the radius of the central or core region of an object or system, measured in parsecs.
-
B.
hasRadiusOfPrimary
Indicates that an entity (typically an orbiting body or system) is associated with a primary object whose radius is specified by the related value or entity.
-
C.
hasCoreArea
Indicates that an entity possesses a primary or central area that is fundamental to its structure, function, or focus.
-
D.
hasClusterRadius
Indicates the radius or spatial extent associated with a particular cluster.
-
E.
hasRadiusRange
Indicates that there is a specified minimum and maximum radius within which the related entity or feature falls.
- 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_69e245b6a3ac81908087599eefe3e365 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f182f6484c8190bfe3f7ea894c43d8 |
completed | April 29, 2026, 4:03 a.m. |
| PD | Predicate disambiguation | batch_69ef3b974e7c8190b8be11dbb4518693 |
completed | April 27, 2026, 10:33 a.m. |
Created at: April 17, 2026, 3:50 p.m.