Triple
T24918637
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | List of popes |
E624059
|
entity |
| Predicate | coversFrom |
P157233
|
FINISHED |
| Object | Saint Peter |
—
|
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: Saint Peter | Statement: [List of popes, coversFrom, Saint Peter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coversFrom Context triple: [List of popes, coversFrom, Saint Peter]
-
A.
coversFully
Indicates that one entity completely and without gaps encloses, spans, or occupies the extent of another entity.
-
B.
coversSection
Indicates that one entity includes, addresses, or provides content for a particular section of another entity.
-
C.
isCoveredIn
Indicates that one entity has its surface or area overlaid, coated, or blanketed by another substance or material.
-
D.
doubleCoveredBy
Indicates that an entity is fully covered or overlapped twice by another entity or pair of entities, such that it is included in two distinct covering relationships.
-
E.
coversRight
Indicates that one entity extends over, protects, or conceals the right side of 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_69e2fac889c081908e9ff686cb428e5a |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f4238e43c08190be03e813b8cdfe28 |
completed | May 1, 2026, 3:52 a.m. |
| PD | Predicate disambiguation | batch_69f4210130d08190ae30b7943f7a0bbc |
completed | May 1, 2026, 3:41 a.m. |
| PDg | Predicate description generation | batch_69f423637bec8190a1701421ac86a3b7 |
completed | May 1, 2026, 3:52 a.m. |
Created at: April 18, 2026, 5:28 a.m.