Triple
T17991303
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Notanthophora |
E430378
|
entity |
| Predicate | hasTribeCommonName |
P130040
|
FINISHED |
| Object | digger bees |
—
|
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: digger bees | Statement: [Notanthophora, hasTribeCommonName, digger bees]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTribeCommonName Context triple: [Notanthophora, hasTribeCommonName, digger bees]
-
A.
hasCommunalAppellation
Indicates that an entity shares a common or collective name or designation with a group or community.
-
B.
hasRelatedTribe
Indicates that one tribe is associated or connected to another tribe in some relevant way, such as by kinship, alliance, or shared characteristics.
-
C.
hasTribalAssociation
Indicates that an entity is affiliated with, belongs to, or is formally associated with a particular tribe or tribal group.
-
D.
hasRecognizedTribe
Indicates that an entity is officially acknowledged or designated as a tribe by a relevant authority or governing body.
-
E.
hasTribuneName
Indicates that an entity is associated with or identified by a specific tribune name.
- 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_69d8b90364248190a37381adea932f42 |
completed | April 10, 2026, 8:46 a.m. |
| NER | Named-entity recognition | batch_69e4b29fd7648190b7f09ea60c7b96a8 |
completed | April 19, 2026, 10:46 a.m. |
| PD | Predicate disambiguation | batch_69e3f90039e4819080527f860dca042e |
completed | April 18, 2026, 9:34 p.m. |
| PDg | Predicate description generation | batch_69e42d8d68288190a05dc5d7803cf823 |
completed | April 19, 2026, 1:19 a.m. |
Created at: April 10, 2026, 10:23 a.m.