Triple
T3386038
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hyde Park |
E71303
|
entity |
| Predicate | acquiredInCentury |
P47159
|
FINISHED |
| Object | 16th century |
—
|
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: 16th century | Statement: [Hyde Park, acquiredInCentury, 16th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: acquiredInCentury Context triple: [Hyde Park, acquiredInCentury, 16th century]
-
A.
endedInCentury
Indicates that an event, period, or process concluded during a specified century.
-
B.
compiledInCentury
Indicates that something (such as a work, text, or document) was compiled during a specified century.
-
C.
existedInCentury
Indicates that an entity existed or was present during a specified century.
-
D.
introducedInCentury
Indicates the century during which something (such as an idea, technology, practice, or entity) was first introduced or came into use.
-
E.
developedSinceCentury
Indicates that something began to be developed or came into existence starting from a specified century onward.
- 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_69ad85a8fd9c819095ecedf838d2bf1b |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb662d190819085b211dac85a83b2 |
completed | March 8, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69ada43615f08190ac2275020d157983 |
completed | March 8, 2026, 4:30 p.m. |
| PDg | Predicate description generation | batch_69ada527ff308190813a7ffdcdec4322 |
completed | March 8, 2026, 4:34 p.m. |
Created at: March 8, 2026, 3:14 p.m.