Triple
T23744170
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HD 74739 |
E586765
|
entity |
| Predicate | hasBayerGenitive |
P36412
|
FINISHED |
| Object | Cancri |
—
|
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: Cancri | Statement: [HD 74739, hasBayerGenitive, Cancri]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBayerGenitive Context triple: [HD 74739, hasBayerGenitive, Cancri]
-
A.
iauGenitive
chosen
Indicates a genitive (possessive or belonging) relationship between two entities, where one is owned by, associated with, or derived from the other.
-
B.
hasGrammaticalGender
Indicates that one entity assigns or possesses a specific grammatical gender in relation to another entity (such as a word, phrase, or linguistic unit).
-
C.
hasFemaleFormOf
Indicates that one entity is the specifically female version or form of another, more general or differently gendered entity.
-
D.
hasGenus
Indicates that one entity belongs to, or is classified under, the biological genus represented by the other entity.
-
E.
hasAblativeForm
Indicates that an entity possesses a specific form used for the ablative grammatical case.
- 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_69e24908efb08190bf755c3a9b91f222 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1bcbbcf988190b56d74af4b126bd8 |
completed | April 29, 2026, 8:09 a.m. |
| PD | Predicate disambiguation | batch_69f155f012808190a4b1cbc155558ade |
completed | April 29, 2026, 12:50 a.m. |
Created at: April 17, 2026, 7:12 p.m.