Triple
T3914677
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Polish Manchester |
E88806
|
entity |
| Predicate | analogyType |
P43530
|
FINISHED |
| Object | industrial development |
—
|
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 development | Statement: [Polish Manchester, analogyType, industrial development]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: analogyType Context triple: [Polish Manchester, analogyType, industrial development]
-
A.
viewOnAnalogy
Indicates a relationship where one entity interprets, understands, or evaluates another entity by drawing an analogy to something else.
-
B.
analogousTitle
Indicates that one entity has a title or position that corresponds in role, rank, or function to the title or position held by another entity.
-
C.
usedAsAnalogFor
Indicates that one entity is employed as a comparison or illustrative counterpart to help explain, represent, or understand another entity.
-
D.
relatedType
chosen
Indicates that one entity is connected to another through a specified type or category of relationship.
-
E.
generalizationOf
Indicates that one entity represents a broader, more general concept or category that subsumes or abstracts over another, more specific entity.
- 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_69aed955229881909e85e73ffab1d343 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aef188b474819087680db42b04ecdd |
completed | March 9, 2026, 4:12 p.m. |
| PD | Predicate disambiguation | batch_69aee75eedcc81908088ff4dbb8be56b |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:22 p.m.