Triple
T17357475
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States (during Soviet–Afghan War) |
E421975
|
entity |
| Predicate | supportCharacter |
P127174
|
FINISHED |
| Object | covert |
—
|
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: covert | Statement: [United States (during Soviet–Afghan War), supportCharacter, covert]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportCharacter Context triple: [United States (during Soviet–Afghan War), supportCharacter, covert]
-
A.
supportedByCharacter
Indicates that an entity receives backing, assistance, or endorsement from a specific character.
-
B.
supportingCharacter
Indicates that one entity plays a secondary or assisting role in the story or context relative to another primary entity.
-
C.
supportBaseCharacterization
Indicates that one entity provides justification or foundational evidence for how another entity is characterized or described.
-
D.
supportAgainst
Indicates providing help, resources, or advocacy to oppose or resist a particular target, threat, or adversary.
-
E.
supportsNPCs
Indicates that an entity provides functionality or compatibility for non-player characters (NPCs) within a system or environment.
- 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_69d889d520008190a26917a95bf1c2ea |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43a4976788190b00c00f710be6c46 |
completed | April 19, 2026, 2:13 a.m. |
| PD | Predicate disambiguation | batch_69e3b02662d08190a07d0fb5c04b6f33 |
completed | April 18, 2026, 4:24 p.m. |
| PDg | Predicate description generation | batch_69e3b2a225b08190a50f984caa6513b9 |
completed | April 18, 2026, 4:34 p.m. |
Created at: April 10, 2026, 5:44 a.m.