Triple
T26085681
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Romsey and Wellow |
E657972
|
entity |
| Predicate | sharesAdministrationFor |
P45995
|
FINISHED |
| Object | St Margaret’s Church, East Wellow |
—
|
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: St Margaret’s Church, East Wellow | Statement: [Romsey and Wellow, sharesAdministrationFor, St Margaret’s Church, East Wellow]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesAdministrationFor Context triple: [Romsey and Wellow, sharesAdministrationFor, St Margaret’s Church, East Wellow]
-
A.
sharesAdministrationWith
chosen
Indicates that two entities are jointly managed, governed, or overseen by the same administrative body or authority.
-
B.
sharesControlWith
Indicates that control, authority, or decision-making power over something is jointly held or exercised between the related entities.
-
C.
sharesDivisionWith
Indicates that two entities belong to or operate within the same organizational division.
-
D.
sharesAuthorWith
Indicates that two entities have at least one author in common.
-
E.
sharesWith
Indicates that one entity gives another entity access to or use of something it possesses.
- 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_69ee5bbf0d208190801ee95d4f07fb16 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f74062b9388190b30546cf700a825c |
completed | May 3, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69f73c802b848190b61a416b7488bd96 |
completed | May 3, 2026, 12:16 p.m. |
Created at: April 26, 2026, 7:42 p.m.