Triple
T7221226
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Single Payment Scheme |
E150263
|
entity |
| Predicate | typeOfDecoupling |
P75529
|
FINISHED |
| Object | area-based decoupled payment |
—
|
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: area-based decoupled payment | Statement: [Single Payment Scheme, typeOfDecoupling, area-based decoupled payment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfDecoupling Context triple: [Single Payment Scheme, typeOfDecoupling, area-based decoupled payment]
-
A.
decompositionType
Indicates the specific way in which a whole is broken down into its constituent parts or components.
-
B.
typeOfDivision
Indicates the specific category or kind of division that characterizes how something is separated, organized, or partitioned.
-
C.
typeOfDecoration
Indicates the specific kind or style of decoration associated with an entity or applied in a given context.
-
D.
derivationType
Indicates the specific manner or process by which one entity is derived or obtained from another.
-
E.
hasCoupling
Indicates that two entities are linked or joined together in a way that allows them to interact, transfer, or coordinate motion, energy, or information.
- F. None of above. chosen
Provenance (4 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_69c687effb44819092b95d07d0368c9f |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6e9b2ef8481908ac6608b1faeb1db |
completed | March 27, 2026, 8:33 p.m. |
| PD | Predicate disambiguation | batch_69c6e75f84e481909e7866186ae80cff |
completed | March 27, 2026, 8:23 p.m. |
| PDg | Predicate description generation | batch_69c6e889854481908c765ce2107f2d3a |
completed | March 27, 2026, 8:28 p.m. |
Created at: March 27, 2026, 2:54 p.m.