Triple
T4312978
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Czechoslovak resistance |
E94116
|
entity |
| Predicate | hadPart |
P35
|
FINISHED |
| Object | domestic resistance in the Protectorate of Bohemia and Moravia |
—
|
LITERAL FINISHED |
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: domestic resistance in the Protectorate of Bohemia and Moravia | Statement: [Czechoslovak resistance, hadPart, domestic resistance in the Protectorate of Bohemia and Moravia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadPart Context triple: [Czechoslovak resistance, hadPart, domestic resistance in the Protectorate of Bohemia and Moravia]
-
A.
hadOrgan
Indicates that an entity previously possessed or contained a specific organ as part of its body.
-
B.
hasPart
chosen
Indicates that one entity is a component, segment, or constituent part of another entity.
-
C.
hadMember
Indicates that an entity was formerly a member or part of another entity or group.
-
D.
hasHad
Indicates that an entity previously experienced, possessed, or was involved in something at some point in the past.
-
E.
hadFort
Indicates that an entity possessed, controlled, or contained a fort at some time.
- 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_69b3451886588190a3dd1305ea7c58dc |
completed | March 12, 2026, 10:58 p.m. |
| NER | Named-entity recognition | batch_69b350d8bff88190bcf7dd419d5f4312 |
completed | March 12, 2026, 11:48 p.m. |
| PD | Predicate disambiguation | batch_69b34f4a07b08190a06ada0d9cbb14fb |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:12 p.m.