Triple
T22925054
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elkridge Furnace Complex |
E569278
|
entity |
| Predicate | eraOfPrimaryActivity |
P150281
|
FINISHED |
| Object | 18th 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: 18th century | Statement: [Elkridge Furnace Complex, eraOfPrimaryActivity, 18th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eraOfPrimaryActivity Context triple: [Elkridge Furnace Complex, eraOfPrimaryActivity, 18th century]
-
A.
lastKnownActivity
Indicates the most recent recorded action, event, or state associated with an entity.
-
B.
targetActivity
Indicates that one entity is the intended focus or goal of another entity’s action, operation, or process.
-
C.
activityContext
Indicates the situational setting or circumstances in which an activity occurs, such as its purpose, environment, or relevant conditions.
-
D.
isDefaultAppFor
Indicates that an application is designated as the primary or automatically chosen program for handling a specific type of content, action, or protocol.
-
E.
exampleApplication
Indicates that something serves as a representative or illustrative instance of how an application is used or functions.
- F. None of above. chosen
Provenance (4 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_69e2458f7d008190901dccbaebeaba24 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f180d84fc08190b747c3f9052c657a |
completed | April 29, 2026, 3:54 a.m. |
| PD | Predicate disambiguation | batch_69ef3b7c5fc081909ac50c5c8569cc19 |
completed | April 27, 2026, 10:33 a.m. |
| PDg | Predicate description generation | batch_69ef538a115081908982597f79355840 |
completed | April 27, 2026, 12:16 p.m. |
Created at: April 17, 2026, 3:43 p.m.