Triple
T6476551
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hampton Court Maze |
E146085
|
entity |
| Predicate | hasMaintenance |
P71131
|
FINISHED |
| Object | regular hedge trimming |
—
|
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: regular hedge trimming | Statement: [Hampton Court Maze, hasMaintenance, regular hedge trimming]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMaintenance Context triple: [Hampton Court Maze, hasMaintenance, regular hedge trimming]
-
A.
hasMaintenanceService
Indicates that an entity receives or is covered by a maintenance service provided by another entity.
-
B.
hasMaintenanceBase
Indicates that an entity is supported, serviced, or maintained at a specific base or maintenance facility.
-
C.
hasMaintenancePort
Indicates that an entity is equipped with a dedicated port or interface used specifically for maintenance, diagnostics, or service operations.
-
D.
hasMaintenanceFacilities
Indicates that one entity provides or contains facilities where the other entity can be serviced, repaired, or maintained.
-
E.
stillMaintained
Indicates that the subject continues to be actively maintained or supported over time.
- 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_69c008fec7408190af7b146dc63d9750 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c06a49b3bc8190ad80c6ca2dd15c68 |
completed | March 22, 2026, 10:16 p.m. |
| PD | Predicate disambiguation | batch_69c0673f6d48819080e10c85155c7195 |
completed | March 22, 2026, 10:03 p.m. |
| PDg | Predicate description generation | batch_69c06822f73081908e6bb9edecbe77a6 |
completed | March 22, 2026, 10:07 p.m. |
Created at: March 22, 2026, 4:51 p.m.