Triple
T13094260
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A. Nugetre |
E310539
|
entity |
| Predicate | nameFormation |
P75423
|
FINISHED |
| Object | reversal of surname "Ertegun" |
—
|
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: reversal of surname "Ertegun" | Statement: [A. Nugetre, nameFormation, reversal of surname "Ertegun"]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nameFormation Context triple: [A. Nugetre, nameFormation, reversal of surname "Ertegun"]
-
A.
typicalWordFormation
Indicates the usual or most common way in which a word is formed from other linguistic elements (such as roots, affixes, or compounds).
-
B.
usesNameForm
Indicates that one entity adopts or applies a particular standardized form or variant of a name associated with another entity.
-
C.
hasWordFormation
chosen
Indicates that one linguistic unit is formed or derived from another through a specific word-formation process (such as compounding, derivation, or affixation).
-
D.
nounFormOf
Indicates that one term is the noun form derived from, or corresponding to, another term (typically a verb or adjective).
-
E.
nameFormInLatin
Indicates that an entity’s name is expressed or recorded in its Latin-language form.
- 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_69d806a733548190989cfd4ce981ca33 |
completed | April 9, 2026, 8:05 p.m. |
| NER | Named-entity recognition | batch_69d9813cd1b881909871a318fdd60672 |
completed | April 10, 2026, 11:01 p.m. |
| PD | Predicate disambiguation | batch_69d9803f6c508190bfadfbc2d00c2c64 |
completed | April 10, 2026, 10:57 p.m. |
Created at: April 9, 2026, 9:03 p.m.