Triple
T2817241
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ermen & Engels |
E54316
|
entity |
| Predicate | basedInCityKnownFor |
P6317
|
FINISHED |
| Object | Manchester as a center of industrial capitalism |
—
|
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: Manchester as a center of industrial capitalism | Statement: [Ermen & Engels, basedInCityKnownFor, Manchester as a center of industrial capitalism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: basedInCityKnownFor Context triple: [Ermen & Engels, basedInCityKnownFor, Manchester as a center of industrial capitalism]
-
A.
basedInCity
chosen
Indicates that an entity has its primary location, headquarters, or main operations situated in a specified city.
-
B.
hasFamousCity
Indicates that an entity possesses or is associated with a city that is widely recognized or renowned.
-
C.
usedInCapitalCityOf
Indicates that something is utilized or applied within the capital city of a specified region or country.
-
D.
representedCity
Indicates that an entity serves as the official representative or proxy for a particular city.
-
E.
notableInCity
Indicates that an entity is particularly prominent, recognized, or significant within a specific city.
- 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_69ab49de0af08190b3da69683be1e728 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abdf15b7288190a03d1193cc0544a6 |
completed | March 7, 2026, 8:17 a.m. |
| PD | Predicate disambiguation | batch_69abdd08f2f481908c3da8a9c7a00552 |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 9:59 p.m.