Triple
T23813899
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Protrepticus |
E589037
|
entity |
| Predicate | traditionallyTitledInLatin |
P9999
|
FINISHED |
| Object | Protrepticus ad Gentes |
—
|
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: Protrepticus ad Gentes | Statement: [Protrepticus, traditionallyTitledInLatin, Protrepticus ad Gentes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionallyTitledInLatin Context triple: [Protrepticus, traditionallyTitledInLatin, Protrepticus ad Gentes]
-
A.
hasLatinTitle
chosen
Indicates that an entity possesses a title or name expressed in Latin.
-
B.
hasLatinTitleOf
Indicates that one entity has, uses, or is associated with the Latin-language title corresponding to another entity.
-
C.
traditionalTitleGivenBy
Indicates that one entity has conferred or assigned a traditional or customary title to another entity.
-
D.
traditionalTitle
Indicates that an entity holds or is associated with a customary or historically established title or honorific within a cultural or social tradition.
-
E.
titleInLatinScript
Indicates that the title of an entity is written or represented using a Latin-based writing system.
- 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_69e25d18619081909c7fb89d8926f14a |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c7a9ce708190a27195d58589d757 |
completed | April 29, 2026, 8:56 a.m. |
| PD | Predicate disambiguation | batch_69f155fe300481909bd617443228df65 |
completed | April 29, 2026, 12:51 a.m. |
Created at: April 17, 2026, 7:57 p.m.