Triple
T11377007
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hercules |
E269493
|
entity |
| Predicate | hasIAUConstellationFamily |
P20368
|
FINISHED |
| Object | Hercules family |
—
|
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: Hercules family | Statement: [Hercules, hasIAUConstellationFamily, Hercules family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIAUConstellationFamily Context triple: [Hercules, hasIAUConstellationFamily, Hercules family]
-
A.
constellationFamily
chosen
Indicates that one constellation belongs to the same traditional family or grouping of constellations as another.
-
B.
parentConstellation
Indicates that one constellation is the larger or primary constellation within which another constellation is contained or of which it is a part.
-
C.
isOneOfIAU88Constellations
Indicates that an entity belongs to the official set of 88 constellations recognized by the International Astronomical Union (IAU).
-
D.
isAsterismOf
Indicates that one or more stars collectively form or belong to a specific asterism.
-
E.
usesConstellation
Indicates that one entity makes use of, relies on, or incorporates a particular constellation in its function, representation, or operation.
- 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_69d6aacca1048190b39dbbc2174616fa |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d800160a1c81909d115bf89fe54a49 |
completed | April 9, 2026, 7:37 p.m. |
| PD | Predicate disambiguation | batch_69d7e7022d508190996f9be0847c2b41 |
completed | April 9, 2026, 5:50 p.m. |
Created at: April 8, 2026, 9:33 p.m.