Triple
T9351850
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lligwy Burial Chamber |
E225036
|
entity |
| Predicate | capstoneDescription |
P88096
|
FINISHED |
| Object | massive stone slab |
—
|
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: massive stone slab | Statement: [Lligwy Burial Chamber, capstoneDescription, massive stone slab]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: capstoneDescription Context triple: [Lligwy Burial Chamber, capstoneDescription, massive stone slab]
-
A.
designDescription
Indicates that an entity has a textual explanation or summary of its design, structure, or intended configuration.
-
B.
capabilityType
Indicates the type or category of capability that an entity possesses or is associated with.
-
C.
capsule
Indicates that one entity is a capsule containing, enclosing, or encapsulating another entity.
-
D.
plannedCapability
Indicates that an entity is intended or scheduled to possess or provide a particular capability in the future.
-
E.
caps
Indicates that one entity serves as the capital city or administrative center of another entity, such as a country, state, or region.
- 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_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. |
| PDg | Predicate description generation | batch_69cc955a38108190b602d1e73725f11b |
completed | April 1, 2026, 3:47 a.m. |
Created at: March 30, 2026, 7:41 p.m.