Triple
T16150786
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Attini |
E391902
|
entity |
| Predicate | notableGroupWithin |
P4297
|
FINISHED |
| Object | fungus-growing ants |
—
|
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: fungus-growing ants | Statement: [Attini, notableGroupWithin, fungus-growing ants]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableGroupWithin Context triple: [Attini, notableGroupWithin, fungus-growing ants]
-
A.
notableSubgroup
chosen
Indicates that one group forms a particularly significant or noteworthy subset within a larger group.
-
B.
notableChildrenGroup
Indicates that an entity has a group of children who are notable or significant in some recognized way.
-
C.
notableOrganizationWithin
Indicates that one organization is a prominent or significant entity operating within the scope, structure, or domain of another organization.
-
D.
notableAreaWithin
Indicates that one area is a particularly significant or noteworthy part located inside another, larger area.
-
E.
notableCommunity
Indicates that an entity is a particularly prominent or significant member of a given community.
- 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_69d87f1c65e48190aa2b4c472e9bafc4 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e21d9724808190a8332987583a345a |
completed | April 17, 2026, 11:46 a.m. |
| PD | Predicate disambiguation | batch_69e1828abb608190a99d86bce1d77de2 |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 5:01 a.m.