Triple
T34699276
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Radzymin |
E1000318
|
entity |
| Predicate | foughtOverBy |
P50503
|
FINISHED |
| Object | Second Polish Republic |
—
|
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: Second Polish Republic | Statement: [Radzymin, foughtOverBy, Second Polish Republic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foughtOverBy Context triple: [Radzymin, foughtOverBy, Second Polish Republic]
-
A.
wasContestedBetween
chosen
Indicates that an event, position, or resource was the subject of competition or dispute involving two or more opposing parties.
-
B.
contestedBy
Indicates that one party challenges, disputes, or opposes a claim, decision, or position held by another party.
-
C.
fought
Indicates that one entity engaged in physical or armed conflict or combat against another entity.
-
D.
wasContestedIn
Indicates that an event, position, or decision was the subject of competition, dispute, or challenge within a particular context or proceeding.
-
E.
battlegroundFor
Indicates that a location serves as the site or arena where a conflict, competition, or struggle between entities takes place.
- 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_69f76dab937881909c86f1b9ad50445f |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f7805ce6208190ac6dbd9c97989978 |
completed | May 3, 2026, 5:05 p.m. |
| PD | Predicate disambiguation | batch_69f77956ec648190ba4fb7e9d83fd107 |
completed | May 3, 2026, 4:35 p.m. |
Created at: May 3, 2026, 3:59 p.m.