Triple
T29062661
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ferae |
E735580
|
entity |
| Predicate | hasMemberSpeciesExample |
P79088
|
FINISHED |
| Object | Canis lupus familiaris |
—
|
NE NERFINISHED |
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: Canis lupus familiaris | Statement: [Ferae, hasMemberSpeciesExample, Canis lupus familiaris]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMemberSpeciesExample Context triple: [Ferae, hasMemberSpeciesExample, Canis lupus familiaris]
-
A.
hasMemberOfSpecies
Indicates that an entity includes, contains, or is associated with one or more individuals belonging to a specified species.
-
B.
includesSpecies
Indicates that one entity contains or encompasses one or more species as part of its composition or scope.
-
C.
belongsToSpecies
Indicates that an individual organism is a member of, or classified under, a particular biological species.
-
D.
includesSpeciesFrom
Indicates that one collection, group, or set contains one or more species that originate from or belong to another specified source or context.
-
E.
memberSpecies
chosen
Indicates that a particular species is a constituent or member of a larger biological or taxonomic group.
- 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_69f077e85498819088b65186550da8cd |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69fd2a215d6c8190a1a428ccaee603f1 |
completed | May 8, 2026, 12:11 a.m. |
| PD | Predicate disambiguation | batch_69fd28ef19688190bb8370f2812a43e7 |
completed | May 8, 2026, 12:06 a.m. |
Created at: April 28, 2026, 10:16 a.m.