Triple
T5023445
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Poikilospermum |
E112911
|
entity |
| Predicate | belongsToFamilyCommonName |
P61588
|
FINISHED |
| Object | hemp family |
—
|
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: hemp family | Statement: [Poikilospermum, belongsToFamilyCommonName, hemp family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToFamilyCommonName Context triple: [Poikilospermum, belongsToFamilyCommonName, hemp family]
-
A.
belongsToFamily
Indicates that an entity is a member of, or is associated as part of, a specific family group.
-
B.
hasFamilyNameOf
Indicates that one entity bears or uses the same family name (surname) as another entity.
-
C.
hasLastNameInCommonWith
Indicates that two entities share the same last name.
-
D.
containsFamily
Indicates that one entity includes or encompasses members of a particular family group within it.
-
E.
canBeFamilyName
Indicates that something is capable of functioning as a family name or surname in at least one context.
- 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_69bd4435c2f48190be593158cbfcf8a3 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd73670578819099a56112950708a8 |
completed | March 20, 2026, 4:18 p.m. |
| PD | Predicate disambiguation | batch_69bd714ecfe08190b5830cfc1c74fa17 |
completed | March 20, 2026, 4:09 p.m. |
| PDg | Predicate description generation | batch_69bd72e1b7cc8190b2e621fdf8f22e38 |
completed | March 20, 2026, 4:16 p.m. |
Created at: March 20, 2026, 1:36 p.m.