Triple
T692165
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Formicidae |
E13817
|
entity |
| Predicate | hasCaste |
P16727
|
FINISHED |
| Object | reproductive queen |
—
|
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: reproductive queen | Statement: [Formicidae, hasCaste, reproductive queen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCaste Context triple: [Formicidae, hasCaste, reproductive queen]
-
A.
hasCase
Indicates that one entity is involved in, associated with, or characterized by a particular case, instance, or occurrence represented by another entity.
-
B.
hasClergyType
Indicates the specific category or role of clergy associated with an entity.
-
C.
hasCP
Indicates that an entity possesses, is associated with, or is characterized by a specific CP (such as a control point, contact person, or configuration parameter), depending on the domain context.
-
D.
hasCultivar
Indicates that one entity is a plant species or variety that possesses, includes, or is associated with a specific cultivated variety (cultivar) as another entity.
-
E.
hasCategoryOn
Indicates that something is assigned to or associated with a specific category within a given context or scope.
- 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_69a493406c408190957eeec9048a8fb6 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a0b05f2c8190876c73db15b489a2 |
completed | March 1, 2026, 8:25 p.m. |
| PD | Predicate disambiguation | batch_69a49d221d38819083c0adda81f59b07 |
completed | March 1, 2026, 8:10 p.m. |
| PDg | Predicate description generation | batch_69a49dc20880819085fa60dc1851f9dc |
completed | March 1, 2026, 8:12 p.m. |
Created at: March 1, 2026, 7:36 p.m.