Triple
T26538848
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Juda |
E671326
|
entity |
| Predicate | colonialAssociation |
P3812
|
FINISHED |
| Object | French sphere of influence |
—
|
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: French sphere of influence | Statement: [Juda, colonialAssociation, French sphere of influence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: colonialAssociation Context triple: [Juda, colonialAssociation, French sphere of influence]
-
A.
keyColonialEntity
Indicates that an entity plays a primary or foundational role within a colonial system, structure, or enterprise.
-
B.
partOfColonialEntity
Indicates that one entity is a constituent or subordinate territorial unit within a larger colonial political or administrative entity.
-
C.
previousColonialInvolvement
Indicates that one entity had a colonial role or presence in another entity at some time in the past.
-
D.
hasColonialHistoryWith
chosen
Indicates that one entity has a historical relationship of colonization or being colonized involving the other entity.
-
E.
isColonial
Indicates that one entity holds or exhibits colonial status, control, or characteristics in relation to another entity 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_69eeb3206e748190b90c85cc81f38c91 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f621fcea1481909b6f8b3af1ee6820 |
completed | May 2, 2026, 4:10 p.m. |
| PD | Predicate disambiguation | batch_69f620debeb48190b7db395fb86cf8d9 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 27, 2026, 1:40 a.m.