Triple
T4849195
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of Asunción |
E108368
|
entity |
| Predicate | hasTypeOfIntegration |
P8841
|
FINISHED |
| Object | common market |
—
|
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: common market | Statement: [Treaty of Asunción, hasTypeOfIntegration, common market]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfIntegration Context triple: [Treaty of Asunción, hasTypeOfIntegration, common market]
-
A.
typeOfIntegration
chosen
Indicates the specific kind or category of integration that exists or is applied between systems, components, or processes.
-
B.
hasTicketIntegration
Indicates that there is an established connection enabling ticket-related data or actions to be shared or synchronized between systems or components.
-
C.
hasServiceType
Indicates that an entity is associated with or categorized by a particular type of service.
-
D.
integratedIn
Indicates that one entity is incorporated as a component or part within a larger system, structure, or context represented by another entity.
-
E.
hasIntegratedTerminal
Indicates that one entity includes or supports a built-in terminal interface as part of its functionality.
- 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_69bd4409b264819085ab855f3eb5381a |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6ddd17d881909f7731ff2b460e83 |
completed | March 20, 2026, 3:55 p.m. |
| PD | Predicate disambiguation | batch_69bd6c2557388190a2d15571bacd24f3 |
completed | March 20, 2026, 3:47 p.m. |
Created at: March 20, 2026, 1:25 p.m.