Triple
T23197660
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Third Level Canal |
E579918
|
entity |
| Predicate | hasIndustryTypeServed |
P112563
|
FINISHED |
| Object | textile manufacturing |
—
|
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: textile manufacturing | Statement: [Third Level Canal, hasIndustryTypeServed, textile manufacturing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIndustryTypeServed Context triple: [Third Level Canal, hasIndustryTypeServed, textile manufacturing]
-
A.
containsIndustry
Indicates that one entity includes or encompasses a particular industry within its scope, structure, or operations.
-
B.
hasCustomerIndustry
Indicates that a customer is associated with or operates within a particular industry or sector.
-
C.
hasPrincipalIndustry
Indicates that an entity’s main or primary industry of operation is the specified industry.
-
D.
supportedIndustry
chosen
Indicates that one entity provides backing, resources, or services to help sustain or advance a particular industry.
-
E.
hasIndustrySection
Indicates that an entity belongs to, is categorized under, or is associated with a particular industry section.
- 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_69e24600eed08190bd7e5295653a1503 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1907770b48190a3194ecce9b45f09 |
completed | April 29, 2026, 5 a.m. |
| PD | Predicate disambiguation | batch_69ef8a041c0081909afb670d17a5aaba |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 17, 2026, 4:06 p.m.