Triple
T35009968
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hidden Valley bunker |
E1009915
|
entity |
| Predicate | canBeSparedBy |
P129301
|
FINISHED |
| Object | NCR (via diplomatic resolution) |
—
|
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: NCR (via diplomatic resolution) | Statement: [Hidden Valley bunker, canBeSparedBy, NCR (via diplomatic resolution)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeSparedBy Context triple: [Hidden Valley bunker, canBeSparedBy, NCR (via diplomatic resolution)]
-
A.
canBeRemovedBy
Indicates that one entity is capable of eliminating, detaching, or undoing another entity or its effect.
-
B.
laterSparedBy
chosen
Indicates that an entity was initially at risk but was subsequently spared or saved by another entity at a later time.
-
C.
isExpendable
Indicates that the entity can be sacrificed, discarded, or removed without causing unacceptable loss or consequence to the overall system or objective.
-
D.
canBeLostBy
Indicates that something is capable of being lost or forfeited by a particular entity.
-
E.
canBeAbolishedBy
Indicates that one entity has the authority or power to formally end, revoke, or eliminate another entity.
- 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_69f76dcc3ac8819096a3ed52f5fa2523 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69feba0f09508190b3e871c62b19ec7f |
completed | May 9, 2026, 4:37 a.m. |
| PD | Predicate disambiguation | batch_69feb957fe7c8190969fb31a6d1a59c8 |
completed | May 9, 2026, 4:34 a.m. |
Created at: May 3, 2026, 4:01 p.m.