Triple
T28566997
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rostenkowski-Wolowitz |
E722705
|
entity |
| Predicate | surnameOriginComponent |
P3325
|
FINISHED |
| Object | Polish-American surname Rostenkowski |
—
|
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: Polish-American surname Rostenkowski | Statement: [Rostenkowski-Wolowitz, surnameOriginComponent, Polish-American surname Rostenkowski]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: surnameOriginComponent Context triple: [Rostenkowski-Wolowitz, surnameOriginComponent, Polish-American surname Rostenkowski]
-
A.
nameOriginExplanation
Indicates that an explanation is provided for the origin or derivation of a given name.
-
B.
patronymicOrigin
Indicates that one entity’s name is derived from the name of a father or paternal ancestor of another entity.
-
C.
patronymOrigin
Indicates that one entity’s name or designation is derived from the name of a father or paternal ancestor.
-
D.
nameEtymologyFor
Indicates that one entity expresses or explains the origin or derivation of the name of another entity.
-
E.
hasNameOrigin
chosen
Indicates that the origin or source of an entity’s name is specified by the related 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_69f01a5f69d08190ad5c0d2167078dec |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f6508f9be0819094d2968611578175 |
completed | May 2, 2026, 7:29 p.m. |
| PD | Predicate disambiguation | batch_69f64cb0d8008190912e1430cfaf92aa |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 28, 2026, 4:07 a.m.