Triple
T37876879
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Formics |
E944747
|
entity |
| Predicate | leadershipClass |
P129072
|
FINISHED |
| Object | Formic queens |
—
|
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: Formic queens | Statement: [Formics, leadershipClass, Formic queens]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leadershipClass Context triple: [Formics, leadershipClass, Formic queens]
-
A.
leaderClass
chosen
Indicates that one entity serves as the primary leader or head within a specified class, group, or category of entities.
-
B.
leadershipContext
Indicates the situational or organizational setting in which leadership is exercised or expressed between entities.
-
C.
documentsLeadership
Indicates that one entity records, evidences, or provides authoritative documentation of another entity’s leadership or leadership role.
-
D.
leadershipFocus
Indicates a relationship where an entity’s attention, priorities, or strategic efforts are directed toward leading, guiding, or influencing others.
-
E.
leader5
Indicates that an entity serves as the primary leader, head, or top authority within a specified group, organization, or context.
- 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_69f76eef55d481908ca6660b4b532550 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fccdd496048190bca801a8a9eecb62 |
completed | May 7, 2026, 5:37 p.m. |
| PD | Predicate disambiguation | batch_69fcccee6240819084680887731ff64b |
completed | May 7, 2026, 5:33 p.m. |
Created at: May 3, 2026, 4:19 p.m.