Triple
T24918638
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | List of popes |
E624059
|
entity |
| Predicate | coversTo |
P157794
|
FINISHED |
| Object | present day |
—
|
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: present day | Statement: [List of popes, coversTo, present day]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coversTo Context triple: [List of popes, coversTo, present day]
-
A.
coversFrom
Indicates that one entity provides protection, concealment, or shelter for another entity against something originating from a specified source or direction.
-
B.
coversRight
Indicates that one entity extends over, protects, or conceals the right side of another entity.
-
C.
coversFully
Indicates that one entity completely and without gaps encloses, spans, or occupies the extent of another entity.
-
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.
isCoveredIn
Indicates that one entity has its surface or area overlaid, coated, or blanketed by another substance or material.
- 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_69f44a417a58819081777e18dda149fd |
completed | May 1, 2026, 6:37 a.m. |
| PD | Predicate disambiguation | batch_69f442b8479c8190a7c8e416ac9e28a0 |
completed | May 1, 2026, 6:05 a.m. |
| PDg | Predicate description generation | batch_69f44a3adb7c8190941572f718b3b93c |
completed | May 1, 2026, 6:37 a.m. |
Created at: April 18, 2026, 5:28 a.m.