Triple
T9351853
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lligwy Burial Chamber |
E225036
|
entity |
| Predicate | capstoneSupport |
P50607
|
FINISHED |
| Object | supported by upright stones |
—
|
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: supported by upright stones | Statement: [Lligwy Burial Chamber, capstoneSupport, supported by upright stones]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: capstoneSupport Context triple: [Lligwy Burial Chamber, capstoneSupport, supported by upright stones]
-
A.
providesSupportTo
Indicates that one entity offers help, resources, or reinforcement to another entity to aid its function, stability, or success.
-
B.
caps
Indicates that one entity serves as the capital city or administrative center of another entity, such as a country, state, or region.
-
C.
supportStructureFor
chosen
Indicates that one entity serves as a physical or functional support structure for another entity.
-
D.
supportsReach
Indicates that one entity enables, facilitates, or maintains the ability of another entity to extend its influence, access, or coverage to additional targets or areas.
-
E.
supportsProject
Indicates that one entity provides assistance, resources, or endorsement to help another entity’s project succeed.
- 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_69ca842abfd48190949d71c3b86eeba8 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd4f93a9848190ad2ae24f2aa607d2 |
completed | April 1, 2026, 5:02 p.m. |
| PD | Predicate disambiguation | batch_69cc7a68ab9481909f97cb70764697cc |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:41 p.m.