Triple
T5741798
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Runway magazine |
E126631
|
entity |
| Predicate | inUniverseIndustry |
P24922
|
FINISHED |
| Object | high fashion |
—
|
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: high fashion | Statement: [Runway magazine, inUniverseIndustry, high fashion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inUniverseIndustry Context triple: [Runway magazine, inUniverseIndustry, high fashion]
-
A.
containsIndustry
Indicates that one entity includes or encompasses a particular industry within its scope, structure, or operations.
-
B.
isPartOfIndustry
Indicates that one entity belongs to, operates within, or is categorized under a particular industry sector.
-
C.
industryContext
chosen
Indicates the industry or sector within which an entity, activity, or relationship is situated or most relevant.
-
D.
inUniverse
Indicates that one entity exists, occurs, or is set within the fictional or conceptual universe defined by another entity.
-
E.
industryConsortium
Indicates a collaborative association where multiple organizations formally join together within an industry to pursue shared goals, standards, or initiatives.
- 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_69c0083179548190b384b0bf3c08ca4d |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c02b52663c8190ab44258468d4296d |
completed | March 22, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69c021ca61688190875bd6107161c284 |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:48 p.m.