Triple
T14950234
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thescelosaurus neglectus |
E372772
|
entity |
| Predicate | genusNameMeaning |
P116804
|
FINISHED |
| Object | "marvelous lizard" for Thescelosaurus |
—
|
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: "marvelous lizard" for Thescelosaurus | Statement: [Thescelosaurus neglectus, genusNameMeaning, "marvelous lizard" for Thescelosaurus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: genusNameMeaning Context triple: [Thescelosaurus neglectus, genusNameMeaning, "marvelous lizard" for Thescelosaurus]
-
A.
speciesNameMeaning
Indicates the meaning or etymological sense of a species’ scientific name.
-
B.
commonNameOfGenus
Indicates that the object is a commonly used name referring to the genus specified by the subject.
-
C.
nomenclaturalTypeGenus
Indicates that one genus serves as the nomenclatural (name-bearing) type for a higher-ranked taxon, anchoring the application and definition of that taxon's name.
-
D.
namedAfterTypeGenus
Indicates that an entity (such as a taxonomic group) is named after its type genus.
-
E.
notableGenus
Indicates that one entity is a genus that is especially prominent, well-known, or significant in relation to the other entity.
- F. None of above. chosen
Provenance (4 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_69d85cca979481908747d2a81eba1cea |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded68fae3c81909873b113bfcaca05 |
completed | April 15, 2026, 12:06 a.m. |
| PD | Predicate disambiguation | batch_69de9a588c2c8190b1245a1c406f447c |
completed | April 14, 2026, 7:49 p.m. |
| PDg | Predicate description generation | batch_69deb1a4d8dc8190a4c0841c20f2875f |
completed | April 14, 2026, 9:29 p.m. |
Created at: April 10, 2026, 2:39 a.m.