Triple
T398978
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Federal Steel Company |
E9236
|
entity |
| Predicate | operatingPeriodStart |
P9196
|
FINISHED |
| Object | late 19th century |
—
|
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: late 19th century | Statement: [Federal Steel Company, operatingPeriodStart, late 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatingPeriodStart Context triple: [Federal Steel Company, operatingPeriodStart, late 19th century]
-
A.
operatedDuring
Indicates that an action, process, or system was functioning or in operation throughout a specified time period or event.
-
B.
operatedAt
Indicates that an operation, procedure, or activity was performed at a specific location or facility.
-
C.
officialOpeningYear
Indicates the calendar year in which something was formally opened or inaugurated for official use.
-
D.
operatedUntil
Indicates that an entity continued to function or be in operation up to a specified end time or date.
-
E.
establishedAt
chosen
Indicates the specific time or date at which something (such as an organization, system, or entity) was founded or brought into existence.
- 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_69a2e8004cb88190b92ed1add6abf41a |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2ec8d0ca881909d786e8eed9b6748 |
completed | Feb. 28, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_69a2e96d17d08190878d3a68b17d51ca |
completed | Feb. 28, 2026, 1:11 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.