Triple
T9575562
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PIX |
E231035
|
entity |
| Predicate | transactionSettlement |
P76197
|
FINISHED |
| Object | instant |
—
|
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: instant | Statement: [PIX, transactionSettlement, instant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transactionSettlement Context triple: [PIX, transactionSettlement, instant]
-
A.
settlementWith
Indicates a relationship where one party reaches or maintains a settlement or agreement with another party, typically resolving a dispute or claim.
-
B.
isSettlementOf
Indicates that one entity is a settlement (such as a town, village, or city) that belongs to, is located within, or is administratively part of another entity.
-
C.
methodOfSettlement
chosen
Indicates the way in which a transaction, obligation, or dispute is resolved, completed, or paid.
-
D.
settlementSystem
Indicates a relationship where a settlement is organized, governed, or structured according to a particular administrative or territorial system.
-
E.
consideredTemporarySettlementOf
Indicates that one location is regarded as a provisional or non-permanent settlement associated with another place.
- 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_69ca848091c48190bc313d6620d09555 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd99aa964c8190a50717edff30f10b |
completed | April 1, 2026, 10:18 p.m. |
| PD | Predicate disambiguation | batch_69ccd59b960c8190966a8870a2426bd5 |
completed | April 1, 2026, 8:21 a.m. |
Created at: March 30, 2026, 8:05 p.m.