Triple
T8671186
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Bauhaus in Chicago |
E205799
|
entity |
| Predicate | importedFrom |
P11260
|
FINISHED |
| Object | Bauhaus educational model |
—
|
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: Bauhaus educational model | Statement: [New Bauhaus in Chicago, importedFrom, Bauhaus educational model]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: importedFrom Context triple: [New Bauhaus in Chicago, importedFrom, Bauhaus educational model]
-
A.
imported
chosen
Indicates that something was brought into a country, system, or context from an external source.
-
B.
importedWith
Indicates that one entity was brought into a system, context, or location together with or as part of another entity during an import process.
-
C.
exportedFrom
Indicates that something has been sent out or shipped from a particular place, source, or origin to another location.
-
D.
incorporatedFrom
Indicates that one entity was formed, established, or legally created by deriving or transforming from another pre-existing entity.
-
E.
importedGeneration
Indicates that electrical energy was generated outside the local system or region and brought in for use through imports.
- 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_69ca83529a9c8190b5c075b4f14636ed |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc4918e3a88190b3c49043211840fd |
completed | March 31, 2026, 10:22 p.m. |
| PD | Predicate disambiguation | batch_69cc4564e018819081036722f3e42a71 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:31 p.m.