Triple
T37471401
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hero’s Rest |
E931160
|
entity |
| Predicate | expansionZone |
P76096
|
FINISHED |
| Object | Bastion |
—
|
NE NERFINISHED |
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: Bastion | Statement: [Hero’s Rest, expansionZone, Bastion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: expansionZone Context triple: [Hero’s Rest, expansionZone, Bastion]
-
A.
expansionZoneContext
Indicates the contextual conditions or parameters under which an expansion zone is defined, interpreted, or applied within a broader system or process.
-
B.
expansionRegion
chosen
Indicates a region or area into which something (such as a structure, process, or influence) is intended or allowed to expand.
-
C.
expansionUnit
Indicates a unit or component that serves to extend, enlarge, or add capacity to another system, structure, or entity.
-
D.
expansionSystem
Indicates a relationship where a system undergoes or enables expansion, typically by increasing its scope, capacity, or components over time.
-
E.
expansionLocation
Indicates the place or area where something grows, spreads, or extends its presence or influence.
- 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_69f76ec2af148190897d101070d7f415 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcf825ca7081909d06b0df33eb33f9 |
completed | May 7, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fcf42160f0819096812a8bf590875e |
completed | May 7, 2026, 8:20 p.m. |
Created at: May 3, 2026, 4:17 p.m.