Triple
T33714361
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | apostolic constitution motu proprio |
E863828
|
entity |
| Predicate | latinTermMeaning |
P38980
|
FINISHED |
| Object | of his own accord |
—
|
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: of his own accord | Statement: [apostolic constitution motu proprio, latinTermMeaning, of his own accord]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: latinTermMeaning Context triple: [apostolic constitution motu proprio, latinTermMeaning, of his own accord]
-
A.
latinMeaning
chosen
Indicates that one entity expresses or specifies the meaning or translation of another entity in Latin.
-
B.
sapereMeaning
Indicates that one entity knows, understands, or is aware of the meaning or sense of another entity.
-
C.
etMeaning
Indicates that one entity expresses or conveys the semantic content or intended sense of another entity (such as a word, phrase, or symbol).
-
D.
lettersMeaning
Indicates that a set of letters or characters represents, signifies, or conveys a particular meaning or message.
-
E.
letterMeaning
Indicates that a particular letter conveys a specific meaning, interpretation, or semantic content.
- 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_69f34989871c81908682e22a2fe4b829 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6ffbad8848190867c2988c0ceb84f |
completed | May 3, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69f6fc5740fc81909774a4f65201a3ff |
completed | May 3, 2026, 7:42 a.m. |
Created at: May 1, 2026, 1:44 a.m.