Triple
T34479005
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | α Capricorni |
E885126
|
entity |
| Predicate | hasProperNameForSystem |
P27536
|
FINISHED |
| Object | Algedi |
E872568
|
NE 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: Algedi | Statement: [α Capricorni, hasProperNameForSystem, Algedi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProperNameForSystem Context triple: [α Capricorni, hasProperNameForSystem, Algedi]
-
A.
hasProperName
chosen
Indicates that an entity is associated with a specific proper name used to uniquely identify it.
-
B.
hasProperNameElement
Indicates that an entity’s proper name includes a specific component (such as a word, phrase, or segment) as one of its constituent elements.
-
C.
usesNamingSystem
Indicates that one entity adopts or applies a particular naming system or convention to identify or label other entities.
-
D.
hasNameGivenBy
Indicates that one entity has a name that was assigned or bestowed by another entity.
-
E.
systematicName
Indicates that one entity is the formal, systematically constructed name assigned to the other entity according to a specific naming convention or standard.
- F. None of above.
Provenance (4 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_69f349c947fc81909d30b53c194d6ea1 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a030c7d03308190a102689db1e8b657 |
completed | May 12, 2026, 11:18 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3729d3dd2c81909adf1346855adcb8 |
completed | June 21, 2026, 12:01 a.m. |
| PD | Predicate disambiguation | batch_6a030a57b16c81909191270f64a77fcf |
completed | May 12, 2026, 11:09 a.m. |
Created at: May 1, 2026, 2:01 a.m.