Triple
T26710448
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stenostiridae |
E673395
|
entity |
| Predicate | hasMemberSpeciesCountApprox |
P20367
|
FINISHED |
| Object | about 10 to 15 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: about 10 to 15 species | Statement: [Stenostiridae, hasMemberSpeciesCountApprox, about 10 to 15 species]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMemberSpeciesCountApprox Context triple: [Stenostiridae, hasMemberSpeciesCountApprox, about 10 to 15 species]
-
A.
numberOfSpecies
Indicates the count of distinct species associated with a given entity or context.
-
B.
hasApproximateMemberCount
chosen
Indicates that an entity is associated with a group or collection for which only an estimated or non-exact number of members is known.
-
C.
hasMemberCountType
Indicates the type or classification used to describe how the number of members in a group or collection is represented.
-
D.
speciesNumber
Indicates the numerical identifier or count associated with a particular species in a given context.
-
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_69eecda3a22881908f3061c760b9d542 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f71f8ee0688190bd025f27993452d3 |
completed | May 3, 2026, 10:12 a.m. |
| PD | Predicate disambiguation | batch_69f71cc405c08190863565609a4c8499 |
completed | May 3, 2026, 10 a.m. |
Created at: April 27, 2026, 3:35 a.m.