Triple
T31799693
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jumelage with Ameland |
E811695
|
entity |
| Predicate | countryOfPartnership |
P200390
|
FINISHED |
| Object | Germany |
—
|
NE NERFINISHED |
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: Germany | Statement: [Jumelage with Ameland, countryOfPartnership, Germany]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: countryOfPartnership Context triple: [Jumelage with Ameland, countryOfPartnership, Germany]
-
A.
countryPartner
Indicates a formal partnership relationship between two countries, such as cooperation, alliance, or strategic collaboration.
-
B.
independencePartner
Indicates that one entity is a partner or collaborator in achieving, supporting, or maintaining the independence or autonomous status of another entity.
-
C.
hasPartnerCountryExample
chosen
Indicates that an entity is associated with an example of a partner country with which it has a collaborative or partnership relationship.
-
D.
partnerInTreaty
Indicates that an entity is a formal participant or signatory in a specific treaty or international agreement.
-
E.
tradePartnerRegion
Indicates that one entity engages in trade with partners located in a specified geographic region.
- 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_69f348e70d188190b4637c5509f81274 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a0004582bb08190b8d0b88251e8d333 |
completed | May 10, 2026, 4:06 a.m. |
| PD | Predicate disambiguation | batch_6a0003e3e5588190933beea5fb28f150 |
completed | May 10, 2026, 4:04 a.m. |
Created at: April 30, 2026, 11:41 p.m.