Triple
T28251655
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | pontifices |
E712324
|
entity |
| Predicate | keptRecordOf |
P72845
|
FINISHED |
| Object | annales maximi |
—
|
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: annales maximi | Statement: [pontifices, keptRecordOf, annales maximi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keptRecordOf Context triple: [pontifices, keptRecordOf, annales maximi]
-
A.
recordKeeper
chosen
Indicates a relationship where one entity is responsible for maintaining, managing, or preserving official records or documented information about another entity or activity.
-
B.
recordEvent
Indicates that an entity logs or stores information about a specific occurrence or action as an event.
-
C.
statusRecordedBy
Indicates that the status of an entity was documented or captured by a specific agent or system.
-
D.
recorded
Indicates that one entity captured, stored, or documented information, audio, video, or data about another entity or event.
-
E.
keptIn
Indicates that one entity is stored, contained, or maintained inside another entity as its location or container.
- 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_69efb5207eb08190827e4c34048030b1 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f643f08e308190bd247db4d494ba59 |
completed | May 2, 2026, 6:35 p.m. |
| PD | Predicate disambiguation | batch_69f641e0fde08190bf06a1c5b388aa84 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 27, 2026, 11:05 p.m.