Triple
T33104769
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | History of Indiana |
E847155
|
entity |
| Predicate | industrialCenters |
P3436
|
FINISHED |
| Object | Indianapolis |
—
|
NE NERFINISHED |
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: Indianapolis | Statement: [History of Indiana, industrialCenters, Indianapolis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: industrialCenters Context triple: [History of Indiana, industrialCenters, Indianapolis]
-
A.
isIndustrialCenter
chosen
Indicates that a place functions as a major hub of industrial activity, production, or manufacturing within a region.
-
B.
industrialStructure
Indicates a structural or organizational relationship involving industrial facilities, systems, or frameworks.
-
C.
isEarlyIndustrialCentreOf
Indicates that a place functioned as an important center of early industrial activity for another specified region or context.
-
D.
industrializedBy
Indicates that an entity has undergone industrial development or transformation as a result of actions carried out by another specified agent or process.
-
E.
industrialComplex
Indicates a relationship where a facility or site functions as a large-scale, integrated center for industrial production, processing, or related operations.
- 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_69f3495686508190b76bf20fa5e00bf7 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6db6af1d88190989810182354d60f |
completed | May 3, 2026, 5:21 a.m. |
| PD | Predicate disambiguation | batch_69f6d82d068c8190940a3200ed760e38 |
completed | May 3, 2026, 5:07 a.m. |
Created at: May 1, 2026, 1:26 a.m.