Triple
T802156
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mollusca |
E17151
|
entity |
| Predicate | hasApproximateSpeciesCount |
P6211
|
FINISHED |
| Object | over 80000 described living species |
—
|
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: over 80000 described living species | Statement: [Mollusca, hasApproximateSpeciesCount, over 80000 described living species]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasApproximateSpeciesCount Context triple: [Mollusca, hasApproximateSpeciesCount, over 80000 described living species]
-
A.
numberOfSpecies
chosen
Indicates the count of distinct species associated with a given entity or context.
-
B.
numberOfGenera
Indicates the total count of genera associated with or contained within a given entity.
-
C.
hasPopulationApproximate
Indicates that an entity has an estimated or approximate population size, rather than an exact count.
-
D.
includesSpecies
Indicates that one entity contains or encompasses one or more species as part of its composition or scope.
-
E.
hasEndemicSpecies
Indicates that a place or region contains species that are native to and found only within that specific geographic area.
- 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_69a49378b9c48190adbf5f62e5b7aca1 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4ace495348190aec66f35ea90bc89 |
completed | March 1, 2026, 9:17 p.m. |
| PD | Predicate disambiguation | batch_69a4aa70973c8190adbf08302d1103a9 |
completed | March 1, 2026, 9:06 p.m. |
Created at: March 1, 2026, 7:38 p.m.