Triple
T25062824
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amsterdam street market tradition |
E627706
|
entity |
| Predicate | includesGoods |
P170325
|
FINISHED |
| Object | fresh vegetables |
—
|
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: fresh vegetables | Statement: [Amsterdam street market tradition, includesGoods, fresh vegetables]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesGoods Context triple: [Amsterdam street market tradition, includesGoods, fresh vegetables]
-
A.
orderIncludes
Indicates that a particular order contains or comprises the specified item(s) or component(s).
-
B.
productIncludes
Indicates that a product contains, comprises, or is composed of the specified component, item, or feature.
-
C.
chargesIncluded
Indicates that the specified charges or fees are already accounted for and included within the referenced amount or agreement.
-
D.
catalogueIncludes
Indicates that a catalogue contains or lists a particular item as part of its contents.
-
E.
includesPayment
Indicates that one entity contains, involves, or provides a monetary payment as part of its terms, contents, or execution.
- F. None of above. chosen
Provenance (4 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_69e2ff2c45f48190afa28369f1df6786 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f69063edbc81909e7735954aabee0b |
completed | May 3, 2026, 12:01 a.m. |
| PD | Predicate disambiguation | batch_69f68b78f29481908cc8f390496dee97 |
completed | May 2, 2026, 11:40 p.m. |
| PDg | Predicate description generation | batch_69f68f6584a88190a8c4d95c0c84bee9 |
completed | May 2, 2026, 11:57 p.m. |
Created at: April 18, 2026, 6:10 a.m.