Triple
T16752622
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Polyergus |
E407120
|
entity |
| Predicate | genusEtymology |
P116804
|
FINISHED |
| Object | name derived from Greek meaning "much-working" or "very active" |
—
|
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: name derived from Greek meaning "much-working" or "very active" | Statement: [Polyergus, genusEtymology, name derived from Greek meaning "much-working" or "very active"]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: genusEtymology Context triple: [Polyergus, genusEtymology, name derived from Greek meaning "much-working" or "very active"]
-
A.
genusNameMeaning
chosen
Indicates the meaning or etymological sense of the name of a genus.
-
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.
speciesNameMeaning
Indicates the meaning or etymological sense of a species’ scientific name.
- 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_69d8838ffb088190a0b11149929006bf |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3aa282bb08190992c9b61caa7a345 |
completed | April 18, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69e319cbd79c8190a03587a61c18bec0 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:21 a.m.