Triple
T25809347
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Martinssen |
E650061
|
entity |
| Predicate | historicalFormationPattern |
P126028
|
FINISHED |
| Object | formed by adding a patronymic suffix to a father’s given name |
—
|
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: formed by adding a patronymic suffix to a father’s given name | Statement: [Martinssen, historicalFormationPattern, formed by adding a patronymic suffix to a father’s given name]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalFormationPattern Context triple: [Martinssen, historicalFormationPattern, formed by adding a patronymic suffix to a father’s given name]
-
A.
historicalFormation
Indicates the process or circumstances through which something came into existence or took shape over time in history.
-
B.
historicalPattern
chosen
Indicates a recurring relationship or sequence of events between entities that has been observed over time.
-
C.
historicallyFormed
Indicates that the relationship or structure arose or developed through historical processes rather than being newly created or purely theoretical.
-
D.
historicalForm
Indicates that one entity is an earlier or historically attested form or variant of another entity.
-
E.
historicalOrigin
Indicates the relationship by which one entity serves as the source, origin, or starting point in history for 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_69e7ab35d264819095367f7e80c983ff |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6ffbad8848190867c2988c0ceb84f |
completed | May 3, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69f6fc53f4f881908dcc698687bbb64d |
completed | May 3, 2026, 7:42 a.m. |
Created at: April 22, 2026, 7:07 a.m.