Triple
T31600095
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Plano Collor |
E806326
|
entity |
| Predicate | depositFreezeDuration |
P86888
|
FINISHED |
| Object | 18 months (planned) |
—
|
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: 18 months (planned) | Statement: [Plano Collor, depositFreezeDuration, 18 months (planned)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: depositFreezeDuration Context triple: [Plano Collor, depositFreezeDuration, 18 months (planned)]
-
A.
freezeUpPeriod
Indicates a time span during which something becomes or remains frozen and unable to move or function normally.
-
B.
rightOfDepositDuration
Indicates that one entity has a right or entitlement that applies for a specified duration following a deposit.
-
C.
thawPeriod
Indicates the time span during which something transitions from a frozen to an unfrozen state.
-
D.
hasFreezingPeriod
chosen
Indicates that an entity is subject to a defined time interval during which freezing (e.g., of assets, operations, or conditions) is in effect.
-
E.
withdrawalGracePeriod
Indicates the time window after an action or event during which a withdrawal can be made without incurring penalties or additional restrictions.
- 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_69f348d54ccc8190a03b5df9a2b40b25 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a837c5c8819084ab09a81c0fc2c6 |
completed | May 3, 2026, 1:43 a.m. |
| PD | Predicate disambiguation | batch_69f6a75656e081908739ed9e2f600e42 |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 30, 2026, 10:32 p.m.