Triple
T10583167
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Limonia crenulata |
E249785
|
entity |
| Predicate | isInFamilyCommonName |
P61588
|
FINISHED |
| Object | citrus 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: citrus family | Statement: [Limonia crenulata, isInFamilyCommonName, citrus family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInFamilyCommonName Context triple: [Limonia crenulata, isInFamilyCommonName, citrus family]
-
A.
belongsToFamilyCommonName
chosen
Indicates that an entity is associated with, or classified under, a particular family-level common name.
-
B.
hasFamilyNameOf
Indicates that one entity bears or uses the same family name (surname) as another entity.
-
C.
includesCommonName
Indicates that one entity contains or specifies a commonly used (non-scientific) name for another entity.
-
D.
inUniverseFamilyName
Indicates that an entity has a specific family surname within a particular fictional or narrative universe.
-
E.
containsFamily
Indicates that one entity includes or encompasses members of a particular family group within it.
- 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_69d381c9d3d48190a29ee491e1696a0e |
completed | April 6, 2026, 9:50 a.m. |
| NER | Named-entity recognition | batch_69d52767d2e0819099511e29e254bc34 |
completed | April 7, 2026, 3:48 p.m. |
| PD | Predicate disambiguation | batch_69d51907b2b881908ab9a8594688ee06 |
completed | April 7, 2026, 2:47 p.m. |
Created at: April 6, 2026, 12:39 p.m.