Triple
T3821271
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atta cephalotes |
E84376
|
entity |
| Predicate | workerCastes |
P17208
|
FINISHED |
| Object | major workers |
—
|
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: major workers | Statement: [Atta cephalotes, workerCastes, major workers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workerCastes Context triple: [Atta cephalotes, workerCastes, major workers]
-
A.
workerCaste
chosen
Indicates a relationship where an entity belongs to or is classified within a particular worker caste or labor-based social group.
-
B.
hasCaste
Indicates that an entity belongs to or is associated with a particular caste within a social or hierarchical system.
-
C.
typicalCasting
Indicates that one entity is the usual or standard casting choice for portraying another entity (such as a role, character, or type).
-
D.
crewType
Indicates the specific role or category of crew associated with an entity, such as the type of personnel assigned to operate or support it.
-
E.
typicalCast
Indicates that the associated entities form the usual or characteristic cast of characters commonly appearing in a given work or type of work.
- 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_69aed931f5908190be2c07af66d4df25 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aef188b474819087680db42b04ecdd |
completed | March 9, 2026, 4:12 p.m. |
| PD | Predicate disambiguation | batch_69aee74a2bc081909b237df8b1e27653 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:17 p.m.