Triple
T22773577
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ottilia |
E563626
|
entity |
| Predicate | nameElementDerivedFrom |
P36773
|
FINISHED |
| Object | Germanic element "aud" (wealth, fortune) |
—
|
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: Germanic element "aud" (wealth, fortune) | Statement: [Ottilia, nameElementDerivedFrom, Germanic element "aud" (wealth, fortune)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nameElementDerivedFrom Context triple: [Ottilia, nameElementDerivedFrom, Germanic element "aud" (wealth, fortune)]
-
A.
nameElement
Indicates that one entity serves as the name or label assigned to another entity or element.
-
B.
nameElementIn
Indicates that an entity is (or contains) a specific name element within a larger naming structure or system.
-
C.
nameElements
Indicates that an entity assigns or specifies the names of multiple elements within a set or structure.
-
D.
nameComesFrom
chosen
Indicates that the name or designation of one entity is derived from, inspired by, or based on another entity.
-
E.
familyNameDerivedFrom
Indicates that one entity’s family name originates from, or is etymologically derived from, another entity.
- 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_69e24554497c819080b996e071de27c2 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17b6040048190a36fa759e06136ea |
completed | April 29, 2026, 3:30 a.m. |
| PD | Predicate disambiguation | batch_69eed2c32e8c8190b73bb9965ed47d64 |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:27 p.m.