Triple
T19261721
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UY Scuti |
E481663
|
entity |
| Predicate | hasSecondaryPeriod |
P135328
|
FINISHED |
| Object | ~1700 days |
—
|
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: ~1700 days | Statement: [UY Scuti, hasSecondaryPeriod, ~1700 days]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSecondaryPeriod Context triple: [UY Scuti, hasSecondaryPeriod, ~1700 days]
-
A.
hasSecondary
Indicates that an entity is associated with an additional or subordinate counterpart beyond its primary one.
-
B.
hasSecond
Indicates that one entity is the second item, position, or element in an ordered sequence or pair relative to another entity.
-
C.
hasSecondarySubject
Indicates that an entity is associated with an additional, non-primary subject in a given context or relationship.
-
D.
hasSecondaryBase
Indicates that an entity possesses or is associated with a secondary or additional base, distinct from its primary base.
-
E.
hasSecondaryPeak
Indicates that an entity exhibits an additional, smaller peak or maximum beyond its primary peak in its profile or behavior.
- 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_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. |
| PDg | Predicate description generation | batch_69e4df51ac6c819091ce72b07790ffa6 |
completed | April 19, 2026, 1:57 p.m. |
Created at: April 10, 2026, 1:28 p.m.