Triple
T148376
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Court |
E3377
|
entity |
| Predicate | isCentralElementOf |
P4751
|
FINISHED |
| Object | Blenheim Palace layout |
—
|
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: Blenheim Palace layout | Statement: [Great Court, isCentralElementOf, Blenheim Palace layout]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCentralElementOf Context triple: [Great Court, isCentralElementOf, Blenheim Palace layout]
-
A.
isCentralTo
Indicates that something plays a primary, essential, or defining role in relation to something else, such that the latter depends on or is organized around it.
-
B.
hasCentralFigure
Indicates that something features a primary or most important figure at its core or focus.
-
C.
centralIn
chosen
Indicates that one entity occupies a central or most important position within another entity, context, or structure.
-
D.
usesElement
Indicates that one entity makes use of, incorporates, or depends on a specified element in its structure, function, or behavior.
-
E.
isBackboneOf
Indicates that one entity forms the main supporting structure or central framework upon which another entity fundamentally depends.
- 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_69a252868de4819080e21c9938bfe8b6 |
completed | Feb. 28, 2026, 2:27 a.m. |
| NER | Named-entity recognition | batch_69a257ecb6f48190992c4c8ca908a81c |
completed | Feb. 28, 2026, 2:50 a.m. |
| PD | Predicate disambiguation | batch_69a256599db08190a7b000b381d32ec4 |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:31 a.m.