Triple
T2377597
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of Guadalupe Hidalgo |
E46232
|
entity |
| Predicate | requiredPayment |
P9211
|
FINISHED |
| Object | 15000000 US dollars |
—
|
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: 15000000 US dollars | Statement: [Treaty of Guadalupe Hidalgo, requiredPayment, 15000000 US dollars]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiredPayment Context triple: [Treaty of Guadalupe Hidalgo, requiredPayment, 15000000 US dollars]
-
A.
requiresPaymentOf
chosen
Indicates that one entity obligates another entity to provide a specified payment as a condition or requirement.
-
B.
creditCheckRequired
Indicates that a verification of an entity’s creditworthiness must be performed before proceeding with a related action or transaction.
-
C.
requiredPledgeFrom
Indicates that one entity mandates or demands a pledge or commitment from another entity as a prerequisite or condition.
-
D.
paidBy
Indicates that a payment or financial obligation is made or settled by the specified entity.
-
E.
requiredBy
Indicates that one entity depends on or cannot function properly without another entity being present, completed, or satisfied.
- 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_69a88a1554a48190a0180682bcf099be |
completed | March 4, 2026, 7:37 p.m. |
| NER | Named-entity recognition | batch_69abca4d89248190be7d712d5fa8382b |
completed | March 7, 2026, 6:48 a.m. |
| PD | Predicate disambiguation | batch_69abc59d82f08190b7c36982d1ae783d |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:57 p.m.