Triple
T23527478
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deneb |
E576472
|
entity |
| Predicate | isSupergiant |
P69915
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Deneb, isSupergiant, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSupergiant Context triple: [Deneb, isSupergiant, true]
-
A.
isBlueSupergiant
Indicates that the subject is a star classified as a blue supergiant, characterized by very high mass, temperature, and luminosity.
-
B.
isGiantStar
chosen
Indicates that a star has an exceptionally large radius and luminosity compared to main-sequence stars, classifying it as a giant star.
-
C.
isGiantSkylander
Indicates that an entity is a member of the Giant class of Skylanders, distinguishing it as a Giant-type Skylander.
-
D.
isBySupergroup
Indicates that something (such as a work, event, or item) is created, performed, or produced by a supergroup, i.e., a group formed from members of other established groups.
-
E.
isPowerhouseIn
Indicates that an entity is a dominant, highly influential, or leading force within a specified domain, context, or location.
- 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_69e245f5a8848190a2ba42e271c6c31f |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1ac74be1881909161b94aa611188a |
completed | April 29, 2026, 7 a.m. |
| PD | Predicate disambiguation | batch_69f1189d75b48190a1c01928a993c9fb |
completed | April 28, 2026, 8:29 p.m. |
Created at: April 17, 2026, 6:09 p.m.