Triple
T4992007
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Walkerburn |
E112152
|
entity |
| Predicate | foundedForIndustry |
P8158
|
FINISHED |
| Object | tweed mills on the River Tweed |
—
|
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: tweed mills on the River Tweed | Statement: [Walkerburn, foundedForIndustry, tweed mills on the River Tweed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundedForIndustry Context triple: [Walkerburn, foundedForIndustry, tweed mills on the River Tweed]
-
A.
foundingIndustry
chosen
Indicates the industry or sector in which an entity was originally founded or began its primary operations.
-
B.
foundedFor
Indicates that an entity was established or created specifically to serve, support, or benefit another entity or purpose.
-
C.
foundedAs
Indicates the original name or form under which an organization, institution, or entity was first established.
-
D.
foundedWith
Indicates that an entity was established or created together with another entity, typically as co-founders or jointly initiated partners.
-
E.
foundedFrom
Indicates that an entity was established or originated starting from a particular source, place, or prior 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_69bd441be7bc8190b530362d427b97d2 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd74249a8c8190952680aee06a9286 |
completed | March 20, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69bd71492dec8190af4c27a3043b35cc |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:34 p.m.