Triple
T37217544
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | α Herculis C |
E922780
|
entity |
| Predicate | isPhysicalCompanionOf |
P69912
|
FINISHED |
| Object | α Herculis B |
—
|
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 B | Statement: [α Herculis C, isPhysicalCompanionOf, α Herculis B]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPhysicalCompanionOf Context triple: [α Herculis C, isPhysicalCompanionOf, α Herculis B]
-
A.
companionOf
Indicates that one entity serves as a companion or partner to another, typically accompanying or being closely associated with them.
-
B.
companionPhysicalAssociation
chosen
Indicates a relationship where one entity is physically accompanying or co-located with another as a companion.
-
C.
wasCompanionOf
Indicates that one entity accompanied or associated closely with another, typically as a partner, ally, or fellow participant over some period of time.
-
D.
hasCompanionSpecies
Indicates that one entity is accompanied by, or exists in association with, another entity of a different species.
-
E.
hasCompanionPiece
Indicates that one item is conceptually or functionally paired with another item as its companion piece.
- 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.