Triple
T9604995
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Salamanca |
E231945
|
entity |
| Predicate | industrialProfile |
P67736
|
FINISHED |
| Object | heavy industry oriented |
—
|
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: heavy industry oriented | Statement: [Salamanca, industrialProfile, heavy industry oriented]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: industrialProfile Context triple: [Salamanca, industrialProfile, heavy industry oriented]
-
A.
industrialFocus
chosen
Indicates a relationship where an entity is primarily concerned with, specialized in, or directed toward a particular industrial sector or area of industrial activity.
-
B.
industrialCategory
Indicates the industry or sector classification to which an entity (such as a business or organization) belongs.
-
C.
hasIndustrialCompany
Indicates that one entity possesses, controls, or is associated with an industrial company.
-
D.
hasIndustrialSector
Indicates that an entity is associated with, operates in, or belongs to a particular industrial sector or branch of economic activity.
-
E.
industryCenter
Indicates that a location functions as a primary hub or focal point for industrial activity or production.
- 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_69ca8484838c8190b2049199d22fef70 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9a5e4a7c8190830b5ad9762ece46 |
completed | April 1, 2026, 10:21 p.m. |
| PD | Predicate disambiguation | batch_69ccd5a6fd2481908efd131e207b8143 |
completed | April 1, 2026, 8:21 a.m. |
Created at: March 30, 2026, 8:08 p.m.