Triple
T25481887
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Centra Spike |
E638596
|
entity |
| Predicate | coverNameFor |
P21109
|
FINISHED |
| Object | Intelligence Support Activity |
—
|
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: Intelligence Support Activity | Statement: [Centra Spike, coverNameFor, Intelligence Support Activity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coverNameFor Context triple: [Centra Spike, coverNameFor, Intelligence Support Activity]
-
A.
coverText
Indicates that one text serves as the cover or front-facing textual representation for another work or resource.
-
B.
coverVersionBy
Indicates that one creative work is a cover version performed or produced by a particular artist or entity.
-
C.
hasCoverName
chosen
Indicates that one entity uses or is known by an alternative, often secret or assumed, name in relation to another entity or context.
-
D.
coverSymbol
Indicates that one symbol or notation is used as a cover or representative marker for another entity in a given context.
-
E.
cover
Indicates that one entity extends over, conceals, protects, or provides a surface or layer for 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_69e75dbabeac8190bab30628f8b799d4 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f777f0548190a3815bcbcf2c614f |
completed | May 2, 2026, 1:09 p.m. |
| PD | Predicate disambiguation | batch_69f5afd5baac8190bb8ed576813c8591 |
completed | May 2, 2026, 8:03 a.m. |
Created at: April 21, 2026, 2:31 p.m.