Triple
T737104
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Darwin family |
E14956
|
entity |
| Predicate | hasTraditionIn |
P19423
|
FINISHED |
| Object | medicine |
—
|
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: medicine | Statement: [Darwin family, hasTraditionIn, medicine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTraditionIn Context triple: [Darwin family, hasTraditionIn, medicine]
-
A.
hasWinningTradition
Indicates that an entity (such as a team or organization) is characterized by a consistent history of success or victories in its competitive activities.
-
B.
traditionSince
Indicates that a tradition has been continuously practiced or recognized starting from a specified point in time.
-
C.
traditionallyOneOf
Indicates that something is customarily or historically considered to belong to a specific set, category, or group.
-
D.
hasTraditionalSymbol
Indicates that something is associated with or represented by a conventional or culturally established symbol.
-
E.
hasTraditionalName
Indicates that an entity is associated with a name traditionally used or recognized for it, often rooted in long-standing cultural or historical practice.
- 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_69a4934d9930819099eed80096b0597d |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a64adf2c81908e48090be35dd9d9 |
completed | March 1, 2026, 8:49 p.m. |
| PD | Predicate disambiguation | batch_69a4a4fc734c81908fbd36386d5746d6 |
completed | March 1, 2026, 8:43 p.m. |
| PDg | Predicate description generation | batch_69a4a64957ec81909fe2e2dbffd80ed3 |
completed | March 1, 2026, 8:49 p.m. |
Created at: March 1, 2026, 7:37 p.m.