Triple
T26045716
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Capurrius |
E647823
|
entity |
| Predicate | latinizedFormOf |
P76738
|
FINISHED |
| Object | Capurro |
—
|
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: Capurro | Statement: [Capurrius, latinizedFormOf, Capurro]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: latinizedFormOf Context triple: [Capurrius, latinizedFormOf, Capurro]
-
A.
nameFormInLatin
Indicates that an entity’s name is expressed or recorded in its Latin-language form.
-
B.
hasLatinizedName
chosen
Indicates that an entity is associated with a version of its name that has been converted into Latin form or spelling.
-
C.
standardizedFormOf
Indicates that one entity is the normalized or officially standardized version of another, often consolidating variations or alternative forms into a single canonical form.
-
D.
laterRomanizedInto
Indicates that an entity’s original form (such as a name, word, or title) was subsequently converted into a later Romanized (Latin-script) version.
-
E.
historicalNameInLatin
Indicates that an entity has a historically used name expressed in Latin.
- 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_69e77e8d419481908004e6318d28aaab |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f6065a844c81908e04d361469aa3c5 |
completed | May 2, 2026, 2:12 p.m. |
| PD | Predicate disambiguation | batch_69f5aff889988190ad10bcf1a280f717 |
completed | May 2, 2026, 8:04 a.m. |
Created at: April 22, 2026, 9:10 a.m.