Triple
T18229
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Western Europe |
E360
|
entity |
| Predicate | hasProcess |
P1410
|
FINISHED |
| Object | economic integration |
—
|
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: economic integration | Statement: [Western Europe, hasProcess, economic integration]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProcess Context triple: [Western Europe, hasProcess, economic integration]
-
A.
usedProcess
Indicates that an entity employed or applied a particular process to achieve a result or perform an action.
-
B.
hasLegislativeProcess
Indicates that there exists a specific legislative procedure or set of steps governing how laws or regulations are proposed, debated, and enacted for the related entity.
-
C.
hasSession
Indicates that an entity is associated with, participates in, or contains a particular session instance.
-
D.
hasClient
Indicates that an entity maintains a client relationship with another entity, typically as a provider of goods or services.
-
E.
hasView
Indicates that one entity provides a visual perspective or outlook onto another entity or scene.
- 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_69a240778d288190815c0052ebbbcc91 |
completed | Feb. 28, 2026, 1:10 a.m. |
| NER | Named-entity recognition | batch_69a246cbca108190a92478df126d9bf8 |
completed | Feb. 28, 2026, 1:37 a.m. |
| PD | Predicate disambiguation | batch_69a2464f61648190ac690044be194972 |
completed | Feb. 28, 2026, 1:35 a.m. |
| PDg | Predicate description generation | batch_69a246cb2904819085c13207565a1db2 |
completed | Feb. 28, 2026, 1:37 a.m. |
Created at: Feb. 28, 2026, 1:14 a.m.