Triple
T2733844
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | In Pace Decus, In Bello Praesidium |
E60380
|
entity |
| Predicate | hasComma |
P11855
|
FINISHED |
| Object | between "Decus" and "In" |
—
|
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: between "Decus" and "In" | Statement: [In Pace Decus, In Bello Praesidium, hasComma, between "Decus" and "In"]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasComma Context triple: [In Pace Decus, In Bello Praesidium, hasComma, between "Decus" and "In"]
-
A.
hasComb
Indicates that an entity possesses or is equipped with a comb.
-
B.
hasBracket
Indicates that one entity possesses, includes, or is associated with a bracket component or structure.
-
C.
hasPar
Indicates a relationship where one entity has another entity as its parent.
-
D.
hasSeparator
chosen
Indicates that one entity includes, uses, or is divided by another entity that serves as a separator or delimiting element.
-
E.
hasComplex
Indicates that one entity possesses, is associated with, or is part of a larger composite structure or complex formed with another entity.
- 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_69ab4b75cd908190b691ef0d1801acda |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abdaf175808190acbbb3873c7c3f67 |
completed | March 7, 2026, 7:59 a.m. |
| PD | Predicate disambiguation | batch_69abd82859348190bce3be8f2e9d60ba |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:56 p.m.