Triple
T16065453
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fermoy |
E389719
|
entity |
| Predicate | garrisonEstablished |
P75677
|
FINISHED |
| Object | late 18th 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: late 18th century | Statement: [Fermoy, garrisonEstablished, late 18th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: garrisonEstablished Context triple: [Fermoy, garrisonEstablished, late 18th century]
-
A.
garrisonOrigin
Indicates that a garrison or stationed military force originates from, or was initially formed in, a specified location or source.
-
B.
garrisonedDuring
chosen
Indicates that a military force was stationed or quartered at a location for defense or control during a specified time period.
-
C.
garrisonTown
Indicates that a town serves as a military base or station where armed forces are permanently or regularly housed.
-
D.
garrisonIncluded
Indicates that a particular garrison is included within, or forms part of, a specified larger military force, unit, or installation.
-
E.
laterGarrisonedBy
Indicates that a location or structure was subsequently occupied and used as a military garrison by a specified force or group.
- 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_69d86daf32ec8190a8c0466c8f49c3c0 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e1858a00888190b8505071575dc56f |
completed | April 17, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69e18272f2288190a17d45fb01cc2b07 |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 4:57 a.m.