Triple
T21885110
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NGC 1300 |
E540384
|
entity |
| Predicate | hasBarLength |
P146053
|
FINISHED |
| Object | ~25000 light-years (approximate) |
—
|
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: ~25000 light-years (approximate) | Statement: [NGC 1300, hasBarLength, ~25000 light-years (approximate)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBarLength Context triple: [NGC 1300, hasBarLength, ~25000 light-years (approximate)]
-
A.
hasUpperBarLength
Indicates that an entity possesses an upper bar whose length is specified or constrained by the related value or object.
-
B.
hasLowerBarLength
Indicates that one entity’s bar length is shorter than the bar length of another entity.
-
C.
hasBarStrength
Indicates that one entity possesses or exhibits a certain level or measure of bar-related strength or robustness in relation to another entity or context.
-
D.
hasBarrelLongerThan
Indicates that one entity’s barrel length is greater than that of another entity.
-
E.
hasBars
Indicates that one entity possesses, contains, or is equipped with bars as a defining feature or component.
- 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_69e0c479a98081908ce333853fdd4348 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f118eabb008190ab6f1364ef4e6feb |
completed | April 28, 2026, 8:30 p.m. |
| PD | Predicate disambiguation | batch_69e6be9a65888190a66598d62d20366c |
completed | April 21, 2026, 12:02 a.m. |
| PDg | Predicate description generation | batch_69e6d054737081908aa7112975b77475 |
completed | April 21, 2026, 1:18 a.m. |
Created at: April 16, 2026, 7:05 p.m.