Triple
T13267573
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anoat sector |
E315960
|
entity |
| Predicate | tradeImportance |
P74963
|
FINISHED |
| Object | minor |
—
|
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: minor | Statement: [Anoat sector, tradeImportance, minor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tradeImportance Context triple: [Anoat sector, tradeImportance, minor]
-
A.
portImportance
Indicates the relative significance or strategic value of a port within a given context (such as trade, logistics, or transportation networks).
-
B.
percentageOfWorldTrade
Indicates the proportion of total global trade that is accounted for by a particular entity or group.
-
C.
countryTradeShare
Indicates the proportion of a country’s total trade that is conducted with a specific partner or in a specific category.
-
D.
tradeBloc
Indicates a formal economic relationship in which entities participate together in a trade bloc, coordinating trade policies and often reducing barriers to commerce among members.
-
E.
hasCommercialImportance
chosen
Indicates that something possesses economic or business value significant enough to impact trade, revenue, or market activity.
- 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_69d806b1d9ac8190852c5571d5bd5f0f |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99cfdc9388190af1fdd3cd4717bd8 |
completed | April 11, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69d98f60911081909fa346a054f76c9f |
completed | April 11, 2026, 12:01 a.m. |
Created at: April 9, 2026, 9:25 p.m.