Triple
T37504011
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Far Reach |
E932043
|
entity |
| Predicate | canBeChainedWith |
P196932
|
FINISHED |
| Object | assassination moves |
—
|
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: assassination moves | Statement: [Far Reach, canBeChainedWith, assassination moves]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeChainedWith Context triple: [Far Reach, canBeChainedWith, assassination moves]
-
A.
supportsChaining
chosen
Indicates that one entity enables or allows another entity to be linked in sequence with additional similar entities, forming a chain of operations or relationships.
-
B.
hasChainFunction
Indicates that an entity possesses or is associated with a specific function or role within a chain or sequence of operations.
-
C.
canBeLinkedTo
Indicates that one entity has the potential or capability to be connected or associated with another entity.
-
D.
canBeInvokedBy
Indicates that one entity (such as a function, method, or operation) is able to be called, triggered, or executed by another entity.
-
E.
canBePassedTo
Indicates that one entity is capable of being transferred, handed over, or given to 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_69f76ec5268481909ea01c73aeeefd42 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff27b125948190aced0fe0189fd39a |
completed | May 9, 2026, 12:25 p.m. |
| PD | Predicate disambiguation | batch_69ff26c30a0481909ef6a54ded851e42 |
completed | May 9, 2026, 12:21 p.m. |
Created at: May 3, 2026, 4:17 p.m.