Triple
T3524442
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ES |
E74503
|
entity |
| Predicate | lastTradingDay |
P23891
|
FINISHED |
| Object | third Friday of the contract month |
—
|
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: third Friday of the contract month | Statement: [ES, lastTradingDay, third Friday of the contract month]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lastTradingDay Context triple: [ES, lastTradingDay, third Friday of the contract month]
-
A.
hasTradingDays
Indicates that an entity is associated with specific days on which trading or commercial transactions are conducted.
-
B.
latestPossibleDate
chosen
Indicates the most recent date on which a given event, condition, or state can validly or feasibly occur.
-
C.
lastEntryDate
Indicates the date on which the most recent entry, record, or update associated with the subject occurred.
-
D.
liquidationDate
Indicates the date on which an entity is formally wound up, dissolved, or its assets are converted to cash in a liquidation process.
-
E.
finalDeliveryDate
Indicates the date on which the last or ultimate delivery in a sequence of deliveries is scheduled or actually occurs.
- 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_69ad85d0c5488190a3d8e02ebd01a1aa |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbc68b15881909b407486946ec3c5 |
completed | March 8, 2026, 6:14 p.m. |
| PD | Predicate disambiguation | batch_69adae121a048190b03825a001d21f49 |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:19 p.m.