Triple
T2435052
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Polish National Catholic Church |
E52939
|
entity |
| Predicate | joinedUnionOfUtrecht |
P39288
|
FINISHED |
| Object | 1907 |
—
|
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: 1907 | Statement: [Polish National Catholic Church, joinedUnionOfUtrecht, 1907]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: joinedUnionOfUtrecht Context triple: [Polish National Catholic Church, joinedUnionOfUtrecht, 1907]
-
A.
unites
Indicates that one entity brings together multiple entities into a single, cohesive whole or shared state.
-
B.
unionEvent
Indicates an event in which two or more entities are joined or combined into a single unified whole.
-
C.
admittedToUnionFrom
Indicates that an entity (such as a state or region) was admitted into a union or larger political entity from a specified prior jurisdiction or status.
-
D.
joinedUNTogetherWith
Indicates that one entity became a member of or affiliated with the University of North Texas together with another entity, at the same time or as part of the same event.
-
E.
wasUnifiedWith
Indicates that two or more previously separate entities were brought together to form a single unified whole.
- 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_69ab4959bcc0819083246f9fb10439e3 |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abcebf7cac8190889e6890d72c256c |
completed | March 7, 2026, 7:07 a.m. |
| PD | Predicate disambiguation | batch_69abc5ac11b081908ce6a506e81a742a |
completed | March 7, 2026, 6:29 a.m. |
| PDg | Predicate description generation | batch_69abcebe7dd08190b197a2a0e78787e3 |
completed | March 7, 2026, 7:07 a.m. |
Created at: March 6, 2026, 9:43 p.m.