Triple
T17021486
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British world-system |
E412955
|
entity |
| Predicate | hadPeriphery |
P125540
|
FINISHED |
| Object | Asian colonies |
—
|
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: Asian colonies | Statement: [British world-system, hadPeriphery, Asian colonies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadPeriphery Context triple: [British world-system, hadPeriphery, Asian colonies]
-
A.
hadMember
Indicates that an entity was formerly a member or part of another entity or group.
-
B.
hadFort
Indicates that an entity possessed, controlled, or contained a fort at some time.
-
C.
hasDunes
Indicates that one entity (typically a geographic area or surface) possesses or is characterized by sand dunes.
-
D.
hadCustom
Indicates that an entity previously possessed or was associated with a customized or user-defined version of something.
-
E.
hadOrgan
Indicates that an entity previously possessed or contained a specific organ as part of its body.
- 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_69d886cc4170819093deddc7b8b4b6a7 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d5d0dc848190a267f8542dfb86a6 |
completed | April 18, 2026, 7:04 p.m. |
| PD | Predicate disambiguation | batch_69e35d5be7f48190af9db67a1e23850f |
completed | April 18, 2026, 10:30 a.m. |
| PDg | Predicate description generation | batch_69e3753f93c88190808fec5692f66699 |
completed | April 18, 2026, 12:12 p.m. |
Created at: April 10, 2026, 5:33 a.m.