Triple
T30171405
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stephanus numbers |
E766929
|
entity |
| Predicate | baseEditionPublishedIn |
P44721
|
FINISHED |
| Object | Geneva |
—
|
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: Geneva | Statement: [Stephanus numbers, baseEditionPublishedIn, Geneva]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: baseEditionPublishedIn Context triple: [Stephanus numbers, baseEditionPublishedIn, Geneva]
-
A.
hasEditionIn
chosen
Indicates that one entity has a specific edition or version that exists or is available in another entity (such as a particular format, language, or location).
-
B.
editionPublicationYear
Indicates the calendar year in which a particular edition of a work was published.
-
C.
publishedEdition
Indicates that one entity is a specific edition or version that has been formally published of another work or resource.
-
D.
correctedEditionYear
Indicates the year in which a corrected or revised edition of a work was published or released.
-
E.
inceptionOfEdition
Indicates the event or point in time at which a particular edition of a work is first created, initiated, or brought into existence.
- 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_69f2247ba20c81909d34f2bfed706e1e |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67f0c2d248190a12c361305d6f00d |
completed | May 2, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69f673c7a4588190837854f3ef61e6bf |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 29, 2026, 7:24 p.m.