Triple
T16424164
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Polistes nimpha |
E398894
|
entity |
| Predicate | colonyLifecycle |
P120386
|
FINISHED |
| Object | spring to late summer |
—
|
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: spring to late summer | Statement: [Polistes nimpha, colonyLifecycle, spring to late summer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: colonyLifecycle Context triple: [Polistes nimpha, colonyLifecycle, spring to late summer]
-
A.
colonyCycle
chosen
Indicates a recurring pattern or sequence of stages that a colony undergoes over time.
-
B.
colonyStatus
Indicates the political or administrative condition of a territory in relation to a colonizing power, such as whether it is a colony, former colony, or non-colonial.
-
C.
colonyFoundation
Indicates the event or process by which a colony is established or founded in a particular place by a founding entity.
-
D.
colonyType
Indicates the specific classification or kind of colony associated with an entity (e.g., its organizational or structural type).
-
E.
colonySize
Indicates the number of individuals or units that make up a colony in the described 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_69d87f2b9024819085c20e52de95d583 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e328f9da9081908dadbdac4b2d38ec |
completed | April 18, 2026, 6:47 a.m. |
| PD | Predicate disambiguation | batch_69e22701d2288190bf8676050758f172 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:09 a.m.