Triple
T5516503
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gegenbaur, 1859 |
E144695
|
entity |
| Predicate | typeOfAuthorship |
P50370
|
FINISHED |
| Object | originalDescription |
—
|
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: originalDescription | Statement: [Gegenbaur, 1859, typeOfAuthorship, originalDescription]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfAuthorship Context triple: [Gegenbaur, 1859, typeOfAuthorship, originalDescription]
-
A.
authorshipStatus
Indicates the current state or condition of an entity’s role as an author in relation to a work (e.g., confirmed, disputed, anonymous, or pending).
-
B.
hasAuthorType
Indicates that an entity is associated with an author characterized by a specific role, category, or type.
-
C.
authorshipInitially
chosen
Indicates that an entity is the original or first author/creator of another entity before any subsequent authorship changes or contributions.
-
D.
authorshipEvidence
Indicates evidence or justification supporting a claim that one entity is the author or creator of another.
-
E.
hasWrittenWorkType
Indicates that an entity (typically a written work) is associated with a specific type or category of written work (such as novel, article, report, etc.).
- 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_69c008f77ff88190b0cd50ca207295d1 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c01f5e8ce08190b7f5f2131bebcd4f |
completed | March 22, 2026, 4:57 p.m. |
| PD | Predicate disambiguation | batch_69c01b0a06348190b39ac9fe80d2836a |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:33 p.m.