Triple
T36374629
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abbeycwmhir |
E895865
|
entity |
| Predicate | refoundedIn |
P9526
|
FINISHED |
| Object | 1176 |
—
|
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: 1176 | Statement: [Abbeycwmhir, refoundedIn, 1176]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: refoundedIn Context triple: [Abbeycwmhir, refoundedIn, 1176]
-
A.
refoundedBy
Indicates that an entity was re-established or reconstituted by another entity after a period of inactivity, dissolution, or significant change.
-
B.
laterRefoundedAs
Indicates that an entity was dissolved or ceased to exist and was subsequently re-established under a new or modified form, identity, or organization.
-
C.
foundedAfterDestructionOf
Indicates that one entity was founded only after the destruction or demise of another entity.
-
D.
reestablishedInYear
Indicates that an entity, previously existing and then discontinued or dissolved, was brought back into existence or operation in the specified year.
-
E.
reFoundationDate
chosen
Indicates the date on which an entity was re-established or founded again after a previous foundation.
- 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_69f76e5115588190ad8738860b7bc68b |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7bb3ff1b08190802b1063d55d3923 |
completed | May 3, 2026, 9:16 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a611a081908dd6aec1df3f4d7f |
completed | May 3, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:10 p.m.