Triple
T4605137
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Palsgraf v. Long Island Railroad Co. |
E100412
|
entity |
| Predicate | timePeriodOfIncident |
P302
|
FINISHED |
| Object | early 1920s |
—
|
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: early 1920s | Statement: [Palsgraf v. Long Island Railroad Co., timePeriodOfIncident, early 1920s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timePeriodOfIncident Context triple: [Palsgraf v. Long Island Railroad Co., timePeriodOfIncident, early 1920s]
-
A.
timeOfInitiation
Indicates the specific point in time at which an action, event, or process begins.
-
B.
timePeriod
chosen
Indicates the specific span or interval of time during which an event, state, or relationship occurs or is valid.
-
C.
timePeriodEvent
Indicates that an event occurs, is scheduled, or is valid within a specified time period.
-
D.
injuryOccurredAt
Indicates that an injury took place at a specific location or during a particular event or time.
-
E.
timeHorizonOfImpact
Indicates the span of time over which an action, event, or factor is expected to produce its effects or consequences.
- 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_69bd43cce1e08190a07d53af6a9b6c24 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd5999f9c88190a43309573df61159 |
completed | March 20, 2026, 2:28 p.m. |
| PD | Predicate disambiguation | batch_69bd522e2d5c8190937d0b5574f78f99 |
completed | March 20, 2026, 1:57 p.m. |
Created at: March 20, 2026, 1:12 p.m.