Triple
T4050404
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Metropolitan Park Commission engineers |
E84170
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historical profession |
C7977
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: historical profession Context triple: [Metropolitan Park Commission engineers, instanceOf, historical profession]
-
A.
historical position
chosen
A historical position is a specific role, office, or status held by an individual within a past social, political, or cultural context, defined by its responsibilities, authority, and time period.
-
B.
historical period
A historical period is a span of time characterized by distinct social, political, cultural, or technological conditions that differentiate it from other eras in history.
-
C.
historical process
A historical process is a sequence of interconnected events and developments over time through which social, political, economic, or cultural conditions gradually change.
-
D.
historical material
Historical material is any primary or secondary source—such as documents, artifacts, recordings, or testimonies—created in or about the past that provides evidence for understanding historical events, contexts, and perspectives.
-
E.
historiographical tradition
A historiographical tradition is a coherent, historically developed approach to interpreting and writing about the past, characterized by shared methods, assumptions, and narrative patterns among historians.
- F. None of above.
Provenance (1 batch)
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_69aed930bd5c819083e7dcc14fc44f69 |
completed | March 9, 2026, 2:29 p.m. |
Created at: March 9, 2026, 3:37 p.m.