Triple
T1254370
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regimini Ecclesiae universae |
E26952
|
entity |
| Predicate | belongsToCollection |
P19933
|
FINISHED |
| Object | acts of Pope Paul VI |
—
|
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: acts of Pope Paul VI | Statement: [Regimini Ecclesiae universae, belongsToCollection, acts of Pope Paul VI]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToCollection Context triple: [Regimini Ecclesiae universae, belongsToCollection, acts of Pope Paul VI]
-
A.
belongsToInteraction
Indicates that one entity is part of, or associated as a component within, a specific interaction event or process.
-
B.
hasCollection
Indicates that an entity possesses, maintains, or is associated with a set or group of related items treated as a collection.
-
C.
belongsToCatalogOf
chosen
Indicates that one item is included within, or is a member of, a particular catalog or collection.
-
D.
hasCollectionItemBy
Indicates that an entity possesses or includes a specific item as part of its collection, identified or referenced by some key or identifier.
-
E.
belongsToFamily
Indicates that an entity is a member of, or is associated as part of, a specific family group.
- 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_69a49487a9c48190ba9b05348fd1b53f |
completed | March 1, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69a4bfa5a4cc819093ed686619b572d8 |
completed | March 1, 2026, 10:37 p.m. |
| PD | Predicate disambiguation | batch_69a4bb6c977c8190a2bf3e8b67a59beb |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:47 p.m.