Triple
T1577515
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Russell 1000 Index |
E33686
|
entity |
| Predicate | reconstitutionMonth |
P1167
|
FINISHED |
| Object | June |
—
|
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: June | Statement: [Russell 1000 Index, reconstitutionMonth, June]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reconstitutionMonth Context triple: [Russell 1000 Index, reconstitutionMonth, June]
-
A.
revivedAsMonthly
Indicates that something previously discontinued, paused, or issued at a different frequency has been brought back specifically as a monthly occurrence or series.
-
B.
reconstructedDuring
Indicates that an entity was rebuilt, restored, or significantly repaired within a specified time period or event.
-
C.
monthObserved
chosen
Indicates the month during which an event, observation, or measurement took place.
-
D.
reconstructedIn
Indicates that something has been rebuilt, restored, or re-created within a particular context, location, or medium.
-
E.
reorganizationPeriod
Indicates the time span during which a structural or organizational change is planned, underway, or in effect.
- 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_69a885f27a4c8190a4622252cdf54c00 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a96083e7308190abbf025fe8e43abb |
completed | March 5, 2026, 10:52 a.m. |
| PD | Predicate disambiguation | batch_69a907ba63c88190b60c14dec8d1e40f |
completed | March 5, 2026, 4:34 a.m. |
Created at: March 4, 2026, 7:27 p.m.