Triple
T4528586
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Union conference |
E106239
|
entity |
| Predicate | canBeReorganizedBy |
P57263
|
FINISHED |
| Object | division or General Conference |
—
|
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: division or General Conference | Statement: [Union conference, canBeReorganizedBy, division or General Conference]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeReorganizedBy Context triple: [Union conference, canBeReorganizedBy, division or General Conference]
-
A.
isPartOfReorganization
Indicates that an entity is involved in, or belongs to, a structural or organizational reconfiguration process.
-
B.
reorganizedAs
Indicates that an existing entity has been restructured or reconfigured into a new organizational form or arrangement.
-
C.
reorganizedIn
Indicates that an entity underwent a structural or organizational change within a specified context, time, or framework.
-
D.
canBeRemovedBy
Indicates that one entity is capable of eliminating, detaching, or undoing another entity or its effect.
-
E.
reorganized
Indicates that an entity has changed the structure, order, or arrangement of another entity or set of entities from a previous configuration.
- 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_69bd43f3d6e08190a91824f833d51bbe |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd5779593081908593537b9239e01b |
completed | March 20, 2026, 2:19 p.m. |
| PD | Predicate disambiguation | batch_69bd521cf77c819083852de3094d1377 |
completed | March 20, 2026, 1:56 p.m. |
| PDg | Predicate description generation | batch_69bd56b3e4c88190a7ade3d0ed0ab606 |
completed | March 20, 2026, 2:16 p.m. |
Created at: March 20, 2026, 1:03 p.m.