Triple
T11497532
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southern Portugal |
E272575
|
entity |
| Predicate | hasTypicalProduct |
P3585
|
FINISHED |
| Object | cork |
—
|
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: cork | Statement: [Southern Portugal, hasTypicalProduct, cork]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypicalProduct Context triple: [Southern Portugal, hasTypicalProduct, cork]
-
A.
hasProduct
chosen
Indicates that an entity possesses, offers, or is associated with a particular product.
-
B.
isTypicallySoldAs
Indicates that one entity is commonly offered for sale in the form, packaging, or configuration represented by another entity.
-
C.
hasProductUser
Indicates that a product is associated with or used by a particular user.
-
D.
usesProduct
Indicates that one entity makes use of, applies, or employs a particular product.
-
E.
hasTypicalPlan
Indicates that there is a standard or commonly followed plan, procedure, or course of action typically associated with the given entity or situation.
- 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_69d6aae1b09881909ce2ded3fa0c14fa |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d85de27db081909ccdb4ab0ef75bdb |
completed | April 10, 2026, 2:18 a.m. |
| PD | Predicate disambiguation | batch_69d808736c5c8190899b5b3b2e797f65 |
completed | April 9, 2026, 8:13 p.m. |
Created at: April 8, 2026, 9:36 p.m.