Triple
T7912762
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Russell 1000 Value Index |
E183737
|
entity |
| Predicate | calculationDays |
P64465
|
FINISHED |
| Object | U.S. trading days |
—
|
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: U.S. trading days | Statement: [Russell 1000 Value Index, calculationDays, U.S. trading days]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: calculationDays Context triple: [Russell 1000 Value Index, calculationDays, U.S. trading days]
-
A.
hasDayCount
chosen
Indicates that an entity is associated with a specific number of days, expressing the duration or count of days related to it.
-
B.
occursNumberOfDaysBefore
Indicates that one event or time point happens a specified number of days earlier than another event or time point.
-
C.
possibleLengthDays
Indicates that an entity can have a duration, measured in whole or fractional days, equal to the specified value.
-
D.
timeDifferenceWith
Indicates a relationship where the temporal difference or interval between two time points, events, or entities is specified or measured.
-
E.
calculationTime
Indicates the amount of time required to perform or complete a calculation.
- 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_69ca828dec0c81908b8f55a4dbbb53ff |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3a7383cc819084eab19799209d2e |
completed | March 31, 2026, 3:07 a.m. |
| PD | Predicate disambiguation | batch_69cae92f9498819085277879e59aa072 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 5:04 p.m.