Triple
T38031642
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nyctaginoideae |
E948921
|
entity |
| Predicate | belongsToCommonNameFamily |
P61588
|
FINISHED |
| Object | four o’clock 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: four o’clock family | Statement: [Nyctaginoideae, belongsToCommonNameFamily, four o’clock family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToCommonNameFamily Context triple: [Nyctaginoideae, belongsToCommonNameFamily, four o’clock family]
-
A.
belongsToFamilyCommonName
chosen
Indicates that an entity is associated with, or classified under, a particular family-level common name.
-
B.
belongsToFamily
Indicates that an entity is a member of, or is associated as part of, a specific family group.
-
C.
hasNameInFamily
Indicates that an entity is known or referred to by a particular name within the context of a specific family or familial group.
-
D.
includesCommonName
Indicates that one entity contains or specifies a commonly used (non-scientific) name for another entity.
-
E.
nameIsCommonIn
Indicates that a given name is frequently used or widely occurring within a specified group, region, or context.
- 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_69f76efd1bc48190a729097fe5177b61 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a004c41f13c8190bc47daf6a5ca3949 |
completed | May 10, 2026, 9:13 a.m. |
| PD | Predicate disambiguation | batch_6a004bce3e3081909b35ae5b3bf2b35e |
completed | May 10, 2026, 9:11 a.m. |
Created at: May 3, 2026, 4:20 p.m.