Triple
T33751397
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TVI |
E864849
|
entity |
| Predicate | formerOwnership |
P59297
|
FINISHED |
| Object | Catholic Church in Portugal |
—
|
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: Catholic Church in Portugal | Statement: [TVI, formerOwnership, Catholic Church in Portugal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerOwnership Context triple: [TVI, formerOwnership, Catholic Church in Portugal]
-
A.
formerPartOwnerOf
Indicates that an entity previously held, but no longer holds, a partial ownership stake in another entity.
-
B.
formerOwnerFamily
Indicates that a member of the subject’s family previously owned the object but no longer does.
-
C.
formerSiteOwner
Indicates that one entity previously owned or controlled a particular site but no longer does so.
-
D.
previouslyPossessedBy
chosen
Indicates that an entity was owned or possessed by another entity at some time in the past, but is not necessarily possessed by that entity now.
-
E.
formerAccess
Indicates that an entity previously had access to another entity or resource but no longer does.
- 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_69f3498c35f881909df279ae4270f831 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ffdd05d1908190957deb11392f4595 |
completed | May 10, 2026, 1:19 a.m. |
| PD | Predicate disambiguation | batch_69ffdc0d33c881908b3483bee8a96540 |
completed | May 10, 2026, 1:14 a.m. |
Created at: May 1, 2026, 1:45 a.m.