Triple
T13395441
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tiliaceae |
E319690
|
entity |
| Predicate | includesTraditionalMembers |
P44882
|
FINISHED |
| Object | Tilia |
—
|
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: Tilia | Statement: [Tiliaceae, includesTraditionalMembers, Tilia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesTraditionalMembers Context triple: [Tiliaceae, includesTraditionalMembers, Tilia]
-
A.
eligibleMembers
Indicates that certain entities meet the required criteria or conditions to be considered eligible members of a specified group or category.
-
B.
traditionallyIncludes
chosen
Indicates that something customarily or historically contains or incorporates something else as a standard or expected part.
-
C.
typicalMembers
Indicates that the related entities are representative or characteristic members of a larger group, category, or class.
-
D.
hasTribalMembersFrom
Indicates that an entity includes or is composed of members originating from a specified tribe or tribal group.
-
E.
traditionalMemberRace
Indicates that an entity belongs to a race or ethnic group that is traditionally associated with or historically characteristic of a particular membership or community.
- 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_69d806b943cc8190b6af624d385d7e12 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dba0d892d08190b1b192b93fe3d72d |
completed | April 12, 2026, 1:40 p.m. |
| PD | Predicate disambiguation | batch_69d9a03189908190a784a2755f8d81e1 |
completed | April 11, 2026, 1:13 a.m. |
Created at: April 9, 2026, 9:34 p.m.