Triple
T23125577
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Taurus |
E577018
|
entity |
| Predicate | hasIAUGenitive |
P36412
|
FINISHED |
| Object | Tauri |
—
|
LITERAL 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: Tauri | Statement: [Taurus, hasIAUGenitive, Tauri]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIAUGenitive Context triple: [Taurus, hasIAUGenitive, Tauri]
-
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.
hasGenus
Indicates that one entity belongs to, or is classified under, the biological genus represented by the other entity.
-
C.
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).
-
D.
hasGenderedInheritance
Indicates that inheritance rights or rules differ based on the gender of the individuals involved.
-
E.
usesGentilicFor
Indicates that one entity refers to another using a gentilic (a demonym or term denoting origin, nationality, or regional affiliation).
- 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_69e245f7b0e481909c473ff4e6a54e2c |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18e53ac288190b27fe8064fb576c2 |
completed | April 29, 2026, 4:51 a.m. |
| PD | Predicate disambiguation | batch_69ef89f020588190b43393e048e7eda3 |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 17, 2026, 3:59 p.m.