Triple
T30211834
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Giovanni Czermanik |
E768087
|
entity |
| Predicate | laterRecordsUseName |
P198139
|
FINISHED |
| Object | Giovanni Czermanik |
—
|
NE NERFINISHED |
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: Giovanni Czermanik | Statement: [Giovanni Czermanik, laterRecordsUseName, Giovanni Czermanik]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterRecordsUseName Context triple: [Giovanni Czermanik, laterRecordsUseName, Giovanni Czermanik]
-
A.
laterNamed
Indicates that an entity was given a new name at a later time, linking its original identity to its subsequent name.
-
B.
usedAfterName
Indicates that one element is used or appears immediately after a name in some context or representation.
-
C.
usedAfterNameOf
Indicates that something is used immediately following the mention or specification of a name.
-
D.
previousNameUsedUntil
Indicates that a particular name was used for an entity up to (but not necessarily including) a specified end date or time.
-
E.
laterUsedBy
Indicates that something is subsequently utilized or employed by a specified entity at a later time.
- F. None of above. chosen
Provenance (4 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_69fecd0a732c819097bdd3eb69b6158c |
completed | May 9, 2026, 5:58 a.m. |
| PD | Predicate disambiguation | batch_69fecc0318d481908b5b20598a76a9fe |
completed | May 9, 2026, 5:54 a.m. |
| PDg | Predicate description generation | batch_69fecd091abc8190872974de731a80fa |
completed | May 9, 2026, 5:58 a.m. |
Created at: April 29, 2026, 7:32 p.m.