Triple
T30211835
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Giovanni Czermanik |
E768087
|
entity |
| Predicate | nameConsistencyOverTime |
P149843
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Giovanni Czermanik, nameConsistencyOverTime, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nameConsistencyOverTime Context triple: [Giovanni Czermanik, nameConsistencyOverTime, yes]
-
A.
nameUsedSince
Indicates that a particular name has been in use for an entity starting from a specified point in time.
-
B.
namePreservedIn
chosen
Indicates that an entity’s name has been maintained or carried over unchanged within another entity or context.
-
C.
namedAfterSince
Indicates that one entity has borne the name of another entity starting from a specific point in time.
-
D.
hasSubsequentNameChange
Indicates that an entity undergoes a later change to its name, resulting in a new official designation after the original.
-
E.
namedDuring
Indicates that an entity received its name during a specified time period or event.
- 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_69f2247eb0848190b4032f302d39c0d9 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67ff185488190a49b208e4ac6cf59 |
completed | May 2, 2026, 10:51 p.m. |
| PD | Predicate disambiguation | batch_69f6760216108190bbb708d53a6c2c25 |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 29, 2026, 7:32 p.m.