Triple
T34018787
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chocim |
E872321
|
entity |
| Predicate | fortressLaterControlledBy |
P146581
|
FINISHED |
| Object | Polish-Lithuanian Commonwealth |
—
|
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: Polish-Lithuanian Commonwealth | Statement: [Chocim, fortressLaterControlledBy, Polish-Lithuanian Commonwealth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fortressLaterControlledBy Context triple: [Chocim, fortressLaterControlledBy, Polish-Lithuanian Commonwealth]
-
A.
fortificationsLaterControlledBy
chosen
Indicates that control over certain fortifications passed to a different entity at a later time.
-
B.
fortressDefended
Indicates that a fortress is actively protected against threats or attacks by some defending force.
-
C.
fortressOriginallyBuiltBy
Indicates that a particular fortress was initially constructed by a specified builder or group.
-
D.
containsFortress
Indicates that a location or area includes a fortress within its boundaries.
-
E.
castleHeldBy
Indicates that a particular castle is under the control, possession, or governance of a specified entity.
- 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_69f349a19ad88190ab586f010c804a8f |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f70b966860819089cf92927f47c5f1 |
completed | May 3, 2026, 8:47 a.m. |
| PD | Predicate disambiguation | batch_69f70abe43e08190b2a30930d96247c1 |
completed | May 3, 2026, 8:43 a.m. |
Created at: May 1, 2026, 1:51 a.m.