Triple
T10626851
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Váli |
E250345
|
entity |
| Predicate | timeToMaturity |
P86480
|
FINISHED |
| Object | one day |
—
|
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: one day | Statement: [Váli, timeToMaturity, one day]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeToMaturity Context triple: [Váli, timeToMaturity, one day]
-
A.
maturityDuration
Indicates the length of time required for something to reach its full development, readiness, or maturity.
-
B.
maturesIn
chosen
Indicates that an entity reaches full development, ripeness, or maturity within a specified time period or under certain conditions.
-
C.
mustBeMaturedIn
Indicates that something is required to undergo a maturation process within a specified context, condition, or environment before it is considered ready or valid.
-
D.
maximumBondMaturity
Indicates the longest allowable or actual time period until a bond tied to an entity reaches its maturity date.
-
E.
maturityType
Indicates the kind or category of maturity associated with an entity, such as how or when an obligation, product, or process reaches its full or due state.
- 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_69d6aa5993448190a493b790b8f85010 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6df8207f08190a6362a8ba00988b2 |
completed | April 8, 2026, 11:06 p.m. |
| PD | Predicate disambiguation | batch_69d6dd7fae088190973f70c69738af49 |
completed | April 8, 2026, 10:58 p.m. |
Created at: April 8, 2026, 8:55 p.m.