Triple
T11524826
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seoul–Los Angeles |
E273264
|
entity |
| Predicate | marketImportance |
P74963
|
FINISHED |
| Object | major |
—
|
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: major | Statement: [Seoul–Los Angeles, marketImportance, major]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: marketImportance Context triple: [Seoul–Los Angeles, marketImportance, major]
-
A.
hasCommercialImportance
chosen
Indicates that something possesses economic or business value significant enough to impact trade, revenue, or market activity.
-
B.
marketTrait
Indicates that an entity possesses a particular characteristic, behavior, or attribute relevant to how it functions or is perceived in a market context.
-
C.
marketSize
Indicates the total volume or value of demand for a product, service, or market segment within a defined scope (such as a time period or geographic region).
-
D.
marketModel
Indicates the specific economic or pricing framework under which transactions or interactions in a market are structured and governed.
-
E.
coreMarket
Indicates that an entity serves as the primary or most important market for another entity’s products, services, or activities.
- 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_69d6aae3fbec8190a14632a5df2538b6 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d87fd26648819083de19bcddf8ad69 |
completed | April 10, 2026, 4:42 a.m. |
| PD | Predicate disambiguation | batch_69d80876e5f0819088cff2e72f773cf6 |
completed | April 9, 2026, 8:13 p.m. |
Created at: April 8, 2026, 9:37 p.m.