Triple
T28716532
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apostolica Sollicitudo |
E729974
|
entity |
| Predicate | seeAlsoPerson |
P24766
|
FINISHED |
| Object | Pope Paul VI |
—
|
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: Pope Paul VI | Statement: [Apostolica Sollicitudo, seeAlsoPerson, Pope Paul VI]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seeAlsoPerson Context triple: [Apostolica Sollicitudo, seeAlsoPerson, Pope Paul VI]
-
A.
seeAlsoRole
Indicates that an entity has an additional, related role that should be consulted for further or complementary information.
-
B.
refersToPerson
chosen
Indicates that one entity is making reference to, mentioning, or pointing specifically to a particular person.
-
C.
relatedWorkOfPerson
Indicates that a work (such as a publication, project, or creation) is associated with or produced by a particular person.
-
D.
refersToPersonKnownFor
Indicates that one entity makes reference to a person who is notable or recognized for some specific role, achievement, or characteristic.
-
E.
peopleAssociatedWith
Indicates that there exists some form of connection, involvement, or relationship between the referenced people.
- 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_69f043e7d5a4819094b18aca10b1e024 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f658ee40088190b71e1219407690d0 |
completed | May 2, 2026, 8:05 p.m. |
| PD | Predicate disambiguation | batch_69f65760fd3081908ffe014a5e2bf069 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 5:51 a.m.