Triple
T19882335
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diaspar |
E477806
|
entity |
| Predicate | defenseStatus |
P137693
|
FINISHED |
| Object | protected against external universe |
—
|
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: protected against external universe | Statement: [Diaspar, defenseStatus, protected against external universe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: defenseStatus Context triple: [Diaspar, defenseStatus, protected against external universe]
-
A.
defenseResult
Indicates the outcome or consequence of a defensive action or strategy in response to an attack or threat.
-
B.
defense
Indicates an action or relationship in which an entity protects, guards, or resists against a threat, attack, or criticism from another entity.
-
C.
defenseIncludes
Indicates that a defense strategy, plan, or system contains or incorporates a particular component, measure, or element as part of it.
-
D.
defends
Indicates that one entity protects or supports another entity against attack, criticism, or harm.
-
E.
defenseControl
Indicates that one entity exercises authority over, manages, or directs the defensive capabilities or protective measures of another entity.
- F. None of above. chosen
Provenance (4 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_69d8e51f32b08190b3687f4f60353250 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e658e0ccc88190b6f093035cd6f2a1 |
completed | April 20, 2026, 4:48 p.m. |
| PD | Predicate disambiguation | batch_69e537e8c4e481909fe95d795b4864e7 |
completed | April 19, 2026, 8:15 p.m. |
| PDg | Predicate description generation | batch_69e543c136b081909cab9394b958390a |
completed | April 19, 2026, 9:06 p.m. |
Created at: April 10, 2026, 1:52 p.m.