Triple
T19752438
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NGC 221 |
E474413
|
entity |
| Predicate | effectiveRadius_ly |
P137192
|
FINISHED |
| Object | 3000 |
—
|
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: 3000 | Statement: [NGC 221, effectiveRadius_ly, 3000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: effectiveRadius_ly Context triple: [NGC 221, effectiveRadius_ly, 3000]
-
A.
coreRadius_ly
Indicates the radius of an object's core region measured in light-years.
-
B.
chargeRadius
Indicates the characteristic radial distance around an entity within which its electric charge or charge-related influence is considered effective.
-
C.
hasRadiusRange
Indicates that there is a specified minimum and maximum radius within which the related entity or feature falls.
-
D.
casualtyRadius
Indicates the distance from a central point within which people or objects are likely to be harmed or killed by an event or action.
-
E.
neighborhoodRadius
Indicates the maximum distance around a reference entity within which other entities are considered to be in its neighborhood.
- 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_69d8e51940a0819087bd2996f98da668 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6529bcb8c8190bcca61a53be86757 |
completed | April 20, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69e5305016e08190b9561a96baecb0b8 |
completed | April 19, 2026, 7:43 p.m. |
| PDg | Predicate description generation | batch_69e532bbedf081908d801600e2af94a7 |
completed | April 19, 2026, 7:53 p.m. |
Created at: April 10, 2026, 1:48 p.m.