Triple
T2897369
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ARCIC |
E63972
|
entity |
| Predicate | fosters |
P43862
|
FINISHED |
| Object | Anglican–Roman Catholic relations |
—
|
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: Anglican–Roman Catholic relations | Statement: [ARCIC, fosters, Anglican–Roman Catholic relations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fosters Context triple: [ARCIC, fosters, Anglican–Roman Catholic relations]
-
A.
fosterParents
Indicates a relationship where individuals act as temporary parental caregivers for a child who is not their biological or adopted offspring.
-
B.
fosterChild
Indicates a relationship where one person is the child being cared for and raised by foster parents who are not their biological or legal parents.
-
C.
adopts
Indicates that one entity formally takes another into its care, control, or use, assuming ongoing responsibility or ownership.
-
D.
auntAndFosterMother
Indicates that one person is both the aunt of another person and also serves as that person’s foster mother.
-
E.
adoptiveFamily
Indicates a familial relationship formed through legal adoption rather than biological descent.
- 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_69ab4c45822c8190830c5f2bb97bcfd0 |
completed | March 6, 2026, 9:51 p.m. |
| NER | Named-entity recognition | batch_69abe08e7b248190a6bb0f6999f99c23 |
completed | March 7, 2026, 8:23 a.m. |
| PD | Predicate disambiguation | batch_69abdd17bcdc8190aa47274a50ba4ad4 |
completed | March 7, 2026, 8:08 a.m. |
| PDg | Predicate description generation | batch_69abde0f4c648190b9812e64f30c39da |
completed | March 7, 2026, 8:13 a.m. |
Created at: March 6, 2026, 10:08 p.m.