Triple
T1158196
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Queen’s Chamber |
E24431
|
entity |
| Predicate | shaftDiscovery |
P19729
|
FINISHED |
| Object | shafts discovered to be blocked by stone doors |
—
|
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: shafts discovered to be blocked by stone doors | Statement: [Queen’s Chamber, shaftDiscovery, shafts discovered to be blocked by stone doors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shaftDiscovery Context triple: [Queen’s Chamber, shaftDiscovery, shafts discovered to be blocked by stone doors]
-
A.
shaftCount
Indicates the number of shafts associated with or contained in an object or system.
-
B.
wasDiscoveredAt
Indicates that an entity was found, identified, or uncovered at a specific place or during a particular event or context.
-
C.
discovery
chosen
Indicates the event or process by which one entity finds, uncovers, or identifies something previously unknown or unrecognized.
-
D.
spurType
Indicates the specific kind or category of spur associated with or used by an entity.
-
E.
hasNumberOfSpokes
Indicates the relationship that specifies how many spokes are present in or associated with an object.
- 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_69a494060e148190abb42f971242c197 |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bcab3cd08190ad06ea007042a8fc |
completed | March 1, 2026, 10:24 p.m. |
| PD | Predicate disambiguation | batch_69a4bb525b648190adcb7a29256d3c41 |
completed | March 1, 2026, 10:18 p.m. |
Created at: March 1, 2026, 7:45 p.m.