Triple
T10905212
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Beehive of Industry |
E257550
|
entity |
| Predicate | featureCharacterized |
P662
|
FINISHED |
| Object | industrial identity |
—
|
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: industrial identity | Statement: [The Beehive of Industry, featureCharacterized, industrial identity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featureCharacterized Context triple: [The Beehive of Industry, featureCharacterized, industrial identity]
-
A.
characterizedBy
chosen
Indicates that one entity possesses a defining quality, feature, or attribute expressed by another entity.
-
B.
featuresCharacterWith
Indicates that one entity (such as a work or product) includes or presents a particular character as part of its content.
-
C.
findingCharacterization
Indicates that a finding is being described or classified in terms of its nature, features, or diagnostic significance.
-
D.
projectCharacteristics
Indicates the defining features, qualities, or attributes that characterize a particular project.
-
E.
catalogCharacteristic
Indicates that a catalog has a specific characteristic or attribute associated with it.
- 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_69d6aa8550c8819095508a2ed9acf3db |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d770656c288190828e71600bb0acd4 |
completed | April 9, 2026, 9:24 a.m. |
| PD | Predicate disambiguation | batch_69d70d3d69e08190bb369e9a7927142c |
completed | April 9, 2026, 2:21 a.m. |
Created at: April 8, 2026, 9:22 p.m.