Triple
T29723401
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wall of Life project |
E752117
|
entity |
| Predicate | usesPrimaryStrategy |
P13064
|
FINISHED |
| Object | static defense |
—
|
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: static defense | Statement: [Wall of Life project, usesPrimaryStrategy, static defense]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesPrimaryStrategy Context triple: [Wall of Life project, usesPrimaryStrategy, static defense]
-
A.
usesStrategy
chosen
Indicates that an entity intentionally applies a particular strategy or method to achieve a goal or perform an action.
-
B.
isPrimary
Indicates that one entity holds the main, leading, or most important role or status in relation to another entity or within a given context.
-
C.
usesPrimaryKey
Indicates that one entity relies on or references another entity’s primary key as its main means of identification or linkage.
-
D.
hasPrimaryTactic
Indicates that an entity is associated with its main or most commonly used tactic or method of operation.
-
E.
isPrimarySetFor
Indicates that one entity is designated as the main or default set associated with 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_69f0d628c00c8190ab5ee7e423d7ec3c |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f727afd5d88190ad48735cd1b32787 |
completed | May 3, 2026, 10:47 a.m. |
| PD | Predicate disambiguation | batch_69f72737c42c8190a3f781a5e98868ff |
completed | May 3, 2026, 10:45 a.m. |
Created at: April 28, 2026, 7:37 p.m.