Triple
T17021467
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British world-system |
E412955
|
entity |
| Predicate | structured |
P72652
|
FINISHED |
| Object | international relations |
—
|
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: international relations | Statement: [British world-system, structured, international relations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: structured Context triple: [British world-system, structured, international relations]
-
A.
formed
Indicates that one entity came into existence, shape, or organization as a result of the actions or processes involving another entity.
-
B.
traditionalStructure
chosen
Indicates that something follows or embodies a customary, historically established form, pattern, or organizational framework.
-
C.
plannedStructure
Indicates that one entity is a structure that is intended or designed to be built or established in the future, rather than already existing.
-
D.
serialized
Indicates that one entity has been converted into a sequential, storable or transmittable data format representing its structure or state.
-
E.
structureStyle
Indicates the architectural or design style characterizing how a structure is built or formed.
- 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_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. |
Created at: April 10, 2026, 5:33 a.m.