Triple
T7590071
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Textile City |
E179711
|
entity |
| Predicate | economicSectorLinked |
P47145
|
FINISHED |
| Object | textiles |
—
|
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: textiles | Statement: [Textile City, economicSectorLinked, textiles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: economicSectorLinked Context triple: [Textile City, economicSectorLinked, textiles]
-
A.
associatedWithEconomicSector
chosen
Indicates that an entity has a connection or involvement with a particular economic sector, such as operating, participating, or being relevant within that sector.
-
B.
economicSectorSourceOfWealth
Indicates that a particular economic sector is the primary source from which an entity derives its wealth or income.
-
C.
ownerSector
Indicates the sector or industry category to which the owner of an entity belongs.
-
D.
economicSectorIssue
Indicates that there is a problem, challenge, or concern affecting a particular economic sector.
-
E.
economicLink
Indicates a relationship where entities are connected through economic interactions, dependencies, or exchanges such as trade, investment, or financial flows.
- 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_69c69f335248819093c1006f30513708 |
completed | March 27, 2026, 3:16 p.m. |
| NER | Named-entity recognition | batch_69c6f9b615f481908b2fe7e8aaed81bc |
completed | March 27, 2026, 9:42 p.m. |
| PD | Predicate disambiguation | batch_69c6f4e04c2c8190a889d928515d9b8e |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:53 p.m.