Triple
T7640056
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Silk City |
E172975
|
entity |
| Predicate | historicallyRenownedFor |
P67817
|
FINISHED |
| Object | silk production |
—
|
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: silk production | Statement: [Silk City, historicallyRenownedFor, silk production]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicallyRenownedFor Context triple: [Silk City, historicallyRenownedFor, silk production]
-
A.
traditionallyKnownFor
chosen
Indicates that something is widely and historically recognized or reputed for a particular characteristic, activity, product, or role.
-
B.
historicallyPrizedFor
Indicates that something has been especially valued or esteemed for a particular quality, use, or significance in the past.
-
C.
hasCulturalSignificanceFor
Indicates that something holds particular cultural meaning, value, or importance for a specified group or community.
-
D.
inscriptionFamousFor
Indicates that an inscription is widely recognized or notable specifically because of the referenced feature, event, content, or characteristic.
-
E.
organFamousFor
Indicates that an organ is widely recognized or notable for a particular characteristic, function, or association.
- 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_69c6995360188190968ee57b72a1627f |
completed | March 27, 2026, 2:50 p.m. |
| NER | Named-entity recognition | batch_69c6facc4b5481908697e662b0991e3f |
completed | March 27, 2026, 9:46 p.m. |
| PD | Predicate disambiguation | batch_69c6f4e8cadc8190b7977fcd213954dd |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:57 p.m.