Triple
T2233654
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fur language |
E49227
|
entity |
| Predicate | hasNegationStrategy |
P26929
|
FINISHED |
| Object | verbal suffixes |
—
|
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: verbal suffixes | Statement: [Fur language, hasNegationStrategy, verbal suffixes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNegationStrategy Context triple: [Fur language, hasNegationStrategy, verbal suffixes]
-
A.
usesStrategy
Indicates that an entity intentionally applies a particular strategy or method to achieve a goal or perform an action.
-
B.
negates
chosen
Indicates that one entity denies, contradicts, or renders false the assertion, state, or effect expressed by another.
-
C.
hasElectoralStrategy
Indicates that an entity employs or is associated with a specific plan or approach for winning or influencing an election.
-
D.
hasTradeoff
Indicates that one option or outcome involves a compromise in which gaining certain benefits requires accepting corresponding costs or disadvantages.
-
E.
hasApproachType
Indicates the specific method, strategy, or manner in which an action, process, or interaction is carried out or approached.
- 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_69a88aa84bdc819086df50e9c20b301e |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc0913f1c8190ac9cfeb0f1c84a76 |
completed | March 7, 2026, 6:07 a.m. |
| PD | Predicate disambiguation | batch_69abbdafc07881909101266a33ae7031 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:47 p.m.