Triple
T35675280
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kiegyezés |
E1030839
|
entity |
| Predicate | definedRelationshipBetween |
P8534
|
FINISHED |
| Object | Austria |
—
|
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: Austria | Statement: [Kiegyezés, definedRelationshipBetween, Austria]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definedRelationshipBetween Context triple: [Kiegyezés, definedRelationshipBetween, Austria]
-
A.
definesRelationshipBetween
chosen
Indicates that one entity specifies or establishes the nature, type, or rules of a relationship that exists between two or more other entities.
-
B.
definesRelationshipAs
Indicates that one entity explicitly specifies or establishes the type or nature of the relationship that holds between two or more entities.
-
C.
coversRelationship
Indicates that one entity extends over, includes, or provides encompassing coverage for another entity or set of entities.
-
D.
haveRelationshipWith
Indicates that one entity is in some form of defined relationship or association with another entity.
-
E.
allyRelation
Indicates a cooperative, supportive relationship in which the entities act as allies toward shared or aligned goals.
- 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_69f76e0acfc0819082c8495c2210ce73 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fecb4d02f881909a9ee97ce98000d5 |
completed | May 9, 2026, 5:51 a.m. |
| PD | Predicate disambiguation | batch_69fec9846c1c8190b317f0711f0755db |
completed | May 9, 2026, 5:43 a.m. |
Created at: May 3, 2026, 4:05 p.m.