Triple
T3992960
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Keemun black tea |
E87033
|
entity |
| Predicate | exportHistory |
P18134
|
FINISHED |
| Object | important Chinese export tea |
—
|
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: important Chinese export tea | Statement: [Keemun black tea, exportHistory, important Chinese export tea]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exportHistory Context triple: [Keemun black tea, exportHistory, important Chinese export tea]
-
A.
operatorHistory
Indicates a record of past actions, states, or changes associated with a particular operator over time.
-
B.
ownershipHistory
Indicates the sequence of past and present owners associated with an entity over time.
-
C.
viewOnHistory
Indicates a relationship where an entity’s perspective, interpretation, or opinion about a historical event, period, or subject is expressed or referenced.
-
D.
subsequentHistory
Indicates that one event, state, or record occurs or is recorded after another in time, reflecting its later historical development or outcome.
-
E.
historicalExport
chosen
Indicates that an entity was exported from one place to another during a past or historically significant period.
- 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_69aed94118148190975e6aa4e554cde9 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefb81040481909b22e4c445ecae0f |
completed | March 9, 2026, 4:55 p.m. |
| PD | Predicate disambiguation | batch_69aef8f692008190bf4d637ffc3d3eaa |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:33 p.m.