Triple
T38270992
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Queen’s Hill |
E1021206
|
entity |
| Predicate | garrisonPeriod |
P75677
|
FINISHED |
| Object | 20th 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: 20th century | Statement: [Queen’s Hill, garrisonPeriod, 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: garrisonPeriod Context triple: [Queen’s Hill, garrisonPeriod, 20th century]
-
A.
garrisonedDuring
chosen
Indicates that a military force was stationed or quartered at a location for defense or control during a specified time period.
-
B.
garrisonHistory
Indicates the historical presence, use, or occupation of a location by a military garrison over time.
-
C.
garrisonDuringWar
Indicates that a military force is stationed in a specific location for defense or control during a time of war.
-
D.
garrisonServed
Indicates that a military unit or personnel were stationed at and performed service in a particular garrison or fortified location.
-
E.
garrisonUseUntil
Indicates that a garrison occupies or utilizes a location or resource up to a specified end time or condition.
- 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_69f76dee198c8190bf5109421e47a658 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fcc3321ef081908023590ba70ba0cf |
completed | May 7, 2026, 4:52 p.m. |
| PD | Predicate disambiguation | batch_69fcb0fdc6e08190b05e894c59481a0d |
completed | May 7, 2026, 3:34 p.m. |
Created at: May 3, 2026, 4:30 p.m.