Triple
T29019766
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Holozoa |
E737418
|
entity |
| Predicate | containsColonialLineages |
P196003
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Holozoa, containsColonialLineages, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsColonialLineages Context triple: [Holozoa, containsColonialLineages, true]
-
A.
hasColonialHistory
Indicates that an entity has experienced or participated in a period of colonial rule, control, or administration in relation to another entity.
-
B.
hasColonialName
Indicates that an entity is known by, or has been assigned, a name originating from a colonial power or colonial period.
-
C.
hasColonialHistoryWith
Indicates that one entity has a historical relationship of colonization or being colonized involving the other entity.
-
D.
isColonial
Indicates that one entity holds or exhibits colonial status, control, or characteristics in relation to another entity or context.
-
E.
hasColonialForm
Indicates that one entity possesses or exhibits a colonial form or structure in relation to another.
- 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_69f077ee19f881909af48f9cab00a2e5 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69fe00dad1708190b6522476bebb43af |
completed | May 8, 2026, 3:27 p.m. |
| PD | Predicate disambiguation | batch_69fdfc3717f48190bb50ac2919c8ef95 |
completed | May 8, 2026, 3:07 p.m. |
| PDg | Predicate description generation | batch_69fe00d8d8248190a63c12aa2c2f7c0c |
completed | May 8, 2026, 3:27 p.m. |
Created at: April 28, 2026, 9:48 a.m.