Triple
T2542438
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crataegus |
E57813
|
entity |
| Predicate | hasNumberOfSpecies |
P6211
|
FINISHED |
| Object | hundreds of species (taxonomically complex) |
—
|
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: hundreds of species (taxonomically complex) | Statement: [Crataegus, hasNumberOfSpecies, hundreds of species (taxonomically complex)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNumberOfSpecies Context triple: [Crataegus, hasNumberOfSpecies, hundreds of species (taxonomically complex)]
-
A.
numberOfSpecies
chosen
Indicates the count of distinct species associated with a given entity or context.
-
B.
hasOnlySpecies
Indicates that an entity is associated exclusively with a single specified species and no others.
-
C.
hasSolitarySpecies
Indicates that an entity includes or is associated with species that live or behave predominantly alone rather than in groups.
-
D.
hasDominantSpecies
Indicates that one entity possesses or is characterized by a species that is predominant or most influential within it.
-
E.
includesSpecies
Indicates that one entity contains or encompasses one or more species as part of its composition or scope.
- 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_69ab4a5212d88190b989ce129f2ad87f |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd2bd92f88190bf100c799f62210c |
completed | March 7, 2026, 7:24 a.m. |
| PD | Predicate disambiguation | batch_69abd0c63964819092d5f578195ae8dd |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:47 p.m.