Triple
T16303765
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eisai |
E395854
|
entity |
| Predicate | broughtBackFrom |
P16989
|
FINISHED |
| Object | China tea seeds |
—
|
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: China tea seeds | Statement: [Eisai, broughtBackFrom, China tea seeds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: broughtBackFrom Context triple: [Eisai, broughtBackFrom, China tea seeds]
-
A.
broughtBack
Indicates that an entity caused another entity to return to a previous place, state, or condition.
-
B.
returnedFrom
chosen
Indicates that an entity has come back or been sent back from a specified source, location, or prior state.
-
C.
broughtTo
Indicates that one entity caused another entity or object to be transported or accompanied to a particular destination or recipient.
-
D.
revivedBy
Indicates that an entity has been brought back to life, consciousness, or active state through the action or intervention of another entity.
-
E.
revivedAfter
Indicates that one entity comes back to life or is restored to a living or active state after a period of being dead, inactive, or nonfunctional, following another event or time point.
- 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_69d87f23bb088190a16fbb91a1957ea5 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e25e35157481909e5604b7dae7a2a2 |
completed | April 17, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69e219fa5508819097e9d383348bf174 |
completed | April 17, 2026, 11:31 a.m. |
Created at: April 10, 2026, 5:06 a.m.