Triple
T21704606
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Libertas |
E535739
|
entity |
| Predicate | hasLatinIncipit |
P144990
|
FINISHED |
| Object | Libertas praestantissimum naturae donum |
—
|
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: Libertas praestantissimum naturae donum | Statement: [Libertas, hasLatinIncipit, Libertas praestantissimum naturae donum]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLatinIncipit Context triple: [Libertas, hasLatinIncipit, Libertas praestantissimum naturae donum]
-
A.
hasLatinTitle
Indicates that an entity possesses a title or name expressed in Latin.
-
B.
hasEnglishIncipit
Indicates that an entity has an opening phrase or initial text (incipit) expressed in English.
-
C.
hasLatinRubrics
Indicates that the associated item includes instructional or explanatory text (rubrics) written in Latin.
-
D.
hasLatinTitleOf
Indicates that one entity has, uses, or is associated with the Latin-language title corresponding to another entity.
-
E.
hasLatinInfluence
Indicates that one entity exerts or reflects cultural, linguistic, or stylistic influence derived from Latin on another entity.
- 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_69e0c46b44c0819088ab883ebd44e0e8 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69efb52e4b84819095a24cc9fdca2b8a |
completed | April 27, 2026, 7:12 p.m. |
| PD | Predicate disambiguation | batch_69e6969113cc8190ab69855ef5667e4b |
completed | April 20, 2026, 9:11 p.m. |
| PDg | Predicate description generation | batch_69e69b4aa2b48190830107391e81571a |
completed | April 20, 2026, 9:31 p.m. |
Created at: April 16, 2026, 6:46 p.m.