Triple
T27848567
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Song imperial armies |
E703889
|
entity |
| Predicate | garrisonSystem |
P111963
|
FINISHED |
| Object | regional garrisons |
—
|
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: regional garrisons | Statement: [Song imperial armies, garrisonSystem, regional garrisons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: garrisonSystem Context triple: [Song imperial armies, garrisonSystem, regional garrisons]
-
A.
garrisonFunction
Indicates that an entity serves as a military garrison or base for another entity, providing housing, support, or operational facilities for its forces.
-
B.
garrisonType
Indicates the specific kind or classification of military garrison associated with an entity.
-
C.
garrisonOrTheater
Indicates that one entity serves as a military garrison or theater of operations for another entity.
-
D.
garrisonOrHQ
Indicates that an entity serves as a military garrison or headquarters location for another entity.
-
E.
garrisonIncluded
chosen
Indicates that a particular garrison is included within, or forms part of, a specified larger military force, unit, or installation.
- 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_69ef840d9e3c819093615ebff4ec22be |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f63902f71c8190b26ac186ad00acbf |
completed | May 2, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69f6318ae6f08190b3f85f9201046a15 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 6:09 p.m.