Triple
T37217538
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | α Herculis A |
E922780
|
entity |
| Predicate | isDominantComponentOf |
P69124
|
FINISHED |
| Object | α Herculis |
—
|
NE NERFINISHED |
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: α Herculis | Statement: [α Herculis A, isDominantComponentOf, α Herculis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isDominantComponentOf Context triple: [α Herculis A, isDominantComponentOf, α Herculis]
-
A.
isAComponentOf
chosen
Indicates that one entity functions as a constituent part or sub-unit of another, larger entity.
-
B.
isPublicComponentOf
Indicates that one entity is a publicly accessible or externally visible part or module of another, larger entity or system.
-
C.
isCoreComponentOf
Indicates that something is an essential, foundational part required for the structure, function, or identity of another entity.
-
D.
isComponentAlongWith
Indicates that an entity functions as a component in conjunction with one or more other components, typically forming a combined or complementary unit within a larger whole.
-
E.
isComponentOfNameOf
Indicates that one entity is the name of a component or part belonging to another entity.
- 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_69f76ea6f5288190b8d9988f613811c0 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb55de3b9c8190a7656aeab3c3ffbc |
completed | May 6, 2026, 2:53 p.m. |
| PD | Predicate disambiguation | batch_69fb35bc92e08190bff447624e2df791 |
completed | May 6, 2026, 12:36 p.m. |
Created at: May 3, 2026, 4:15 p.m.