Triple
T29654264
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Terran |
E750225
|
entity |
| Predicate | defensiveMechanic |
P8412
|
FINISHED |
| Object | bunkers |
—
|
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: bunkers | Statement: [Terran, defensiveMechanic, bunkers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: defensiveMechanic Context triple: [Terran, defensiveMechanic, bunkers]
-
A.
defensiveSystem
Indicates a system or mechanism whose primary function is to protect, guard, or defend an entity against threats or attacks.
-
B.
mecha
Indicates a relationship where an entity is a mechanical robot or piloted machine, typically used as a vehicle, weapon, or tool in a technological or sci‑fi context.
-
C.
defensiveCapability
Indicates the ability or capacity of an entity to protect itself or others against threats, attacks, or harm.
-
D.
defensiveStructure
chosen
Indicates a relationship where one entity functions as a structure built or used to protect, defend, or fortify another entity or area.
-
E.
defenceEngineer
Indicates a relationship where an entity works as an engineer specializing in defense-related systems, technologies, or projects.
- 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_69f0d6226fe881908819197c9ef9ee04 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f6db1f3ec48190a82e7d893d3c76ba |
completed | May 3, 2026, 5:20 a.m. |
| PD | Predicate disambiguation | batch_69f6d82adfa481908a5e196d2e18c73f |
completed | May 3, 2026, 5:07 a.m. |
Created at: April 28, 2026, 6:54 p.m.