Triple
T8245199
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nylon |
E192833
|
entity |
| Predicate | wasFamouslyUsedFor |
P58306
|
FINISHED |
| Object | women's stockings |
—
|
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: women's stockings | Statement: [Nylon, wasFamouslyUsedFor, women's stockings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasFamouslyUsedFor Context triple: [Nylon, wasFamouslyUsedFor, women's stockings]
-
A.
isFamouslyUsedBy
Indicates that something is widely and notably used by a particular person, group, or entity, in a way that is broadly recognized or associated with them.
-
B.
isFamouslyUsedIn
chosen
Indicates that something is widely recognized or well-known for being used in a particular context, work, or situation.
-
C.
firstWidelyUsedFor
Indicates that something was the earliest instance to be broadly adopted or commonly used for a particular purpose or application.
-
D.
historicallyUsedFor
Indicates that something served a particular function or purpose at some point in the past, even if it may no longer be used that way now.
-
E.
wasUsedBy
Indicates that something served as a tool, resource, or means for an agent to perform an action or achieve a result.
- 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_69ca82de7b8c81908d8106f8a53cff9b |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7872f6d481909ea1d3c2aad1a2b1 |
completed | March 31, 2026, 7:32 a.m. |
| PD | Predicate disambiguation | batch_69cb36b437e881909958591357e83b9d |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:48 p.m.