Triple
T34028099
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fomalhaut |
E872564
|
entity |
| Predicate | companionDesignation |
P49802
|
FINISHED |
| Object | Fomalhaut 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: Fomalhaut B | Statement: [Fomalhaut, companionDesignation, Fomalhaut B]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: companionDesignation Context triple: [Fomalhaut, companionDesignation, Fomalhaut B]
-
A.
companionOf
Indicates that one entity serves as a companion or partner to another, typically accompanying or being closely associated with them.
-
B.
wasCompanionOf
Indicates that one entity accompanied or associated closely with another, typically as a partner, ally, or fellow participant over some period of time.
-
C.
designationFor
chosen
Indicates that one entity serves as the official title, label, or role name assigned to another entity.
-
D.
hasPartnerDesignation
Indicates that one entity is formally designated as a partner of another entity within a specified context or relationship.
-
E.
companionPhysicalAssociation
Indicates a relationship where one entity is physically accompanying or co-located with another as a companion.
- 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_69f349a2527c81909a7cd4bda94d70ad |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd2a215d6c8190a1a428ccaee603f1 |
completed | May 8, 2026, 12:11 a.m. |
| PD | Predicate disambiguation | batch_69fd28ef19688190bb8370f2812a43e7 |
completed | May 8, 2026, 12:06 a.m. |
Created at: May 1, 2026, 1:51 a.m.