Triple
T16103445
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ruby Ridge, Boundary County, Idaho, United States |
E390679
|
entity |
| Predicate | compensationAmountUSD |
P88497
|
FINISHED |
| Object | 3000000 |
—
|
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: 3000000 | Statement: [Ruby Ridge, Boundary County, Idaho, United States, compensationAmountUSD, 3000000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: compensationAmountUSD Context triple: [Ruby Ridge, Boundary County, Idaho, United States, compensationAmountUSD, 3000000]
-
A.
providedCompensationAmount
chosen
Indicates the specific amount of compensation that was given or agreed to be given in relation to an action, event, or obligation.
-
B.
compensationRate
Indicates the rate or amount of payment provided in exchange for a specified unit of work, time, or service.
-
C.
valueInUSD
Indicates that a given amount or asset is expressed or evaluated in terms of its monetary value in United States dollars (USD).
-
D.
valueInCents
Indicates that one entity specifies the monetary value of another entity expressed in cents.
-
E.
compensationIncludes
Indicates that a specified form of payment or benefit is part of the overall compensation provided in a given context.
- 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_69d87f1a8dd881909f1de6ef78849874 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e1ff6a4b8881908e8dc186381196d8 |
completed | April 17, 2026, 9:37 a.m. |
| PD | Predicate disambiguation | batch_69e182804208819087f35307cd6e4103 |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 5 a.m.