Triple
T37902545
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FSSP |
E945455
|
entity |
| Predicate | canApplyMeasure |
P168745
|
FINISHED |
| Object | seizure of property of debtors |
—
|
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: seizure of property of debtors | Statement: [FSSP, canApplyMeasure, seizure of property of debtors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canApplyMeasure Context triple: [FSSP, canApplyMeasure, seizure of property of debtors]
-
A.
containsMeasure
Indicates that one entity includes or encompasses a specific measure or quantitative component as part of its content or structure.
-
B.
enabledMeasurementOf
Indicates that one entity made it possible or allowed another entity to perform or obtain a specific measurement.
-
C.
implementsMeasure
chosen
Indicates that one entity carries out, applies, or realizes a specified measure, policy, or procedure.
-
D.
hasMeasurement
Indicates that an entity is associated with a specific measured value, often including a unit or measurement context.
-
E.
includesMeasure
Indicates that one entity contains, incorporates, or makes use of a particular measurement or quantitative value as part of its definition or specification.
- 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_69f76ef20bb0819088b5b6ceecb0b8fc |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd166a488190b1bf9316b0790801 |
completed | May 6, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:20 p.m.