Triple
T27466386
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Viktor Orbán (1998–2002) |
E693186
|
entity |
| Predicate | signedInternationalAgreement |
P36683
|
FINISHED |
| Object | NATO accession protocols for Hungary |
—
|
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: NATO accession protocols for Hungary | Statement: [Viktor Orbán (1998–2002), signedInternationalAgreement, NATO accession protocols for Hungary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: signedInternationalAgreement Context triple: [Viktor Orbán (1998–2002), signedInternationalAgreement, NATO accession protocols for Hungary]
-
A.
signedTreatyAt
Indicates that an entity formally entered into and endorsed a treaty at a specific location.
-
B.
internationalAgreementSignedAt
Indicates that an international agreement was formally signed at a specific location.
-
C.
internationalAgreementBasis
Indicates that one entity serves as the legal or formal basis for an international agreement involving another entity.
-
D.
signedMajorTreaty
chosen
Indicates that an entity formally entered into and approved a significant, binding treaty with another party or parties.
-
E.
tradeAgreementSigned
Indicates that a formal trade agreement has been officially concluded and signed between the involved parties.
- 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_69ef538105548190a771cc5a0cf8c211 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f643ed0b7481908cf25f3afec0a61d |
completed | May 2, 2026, 6:35 p.m. |
| PD | Predicate disambiguation | batch_69f641dc8ff48190ab575d855616580c |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 27, 2026, 12:52 p.m.