Triple
T2162313
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fortified Sector of Thionville |
E46827
|
entity |
| Predicate | status1939 |
P19690
|
FINISHED |
| Object | operational |
—
|
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: operational | Statement: [Fortified Sector of Thionville, status1939, operational]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: status1939 Context triple: [Fortified Sector of Thionville, status1939, operational]
-
A.
status
Indicates the current condition, state, or standing of an entity within a given context.
-
B.
statusDuring1939Campaign
chosen
Indicates the role, condition, or state an entity held specifically during the 1939 military campaign.
-
C.
statusInCommunistPoland
Indicates the social, legal, or political standing an entity held within the societal system of communist-era Poland.
-
D.
legalStatusAfterWar
Indicates the legal condition or classification assigned to an entity as a consequence of, or following the conclusion of, a war or armed conflict.
-
E.
statusIn1945
Indicates the condition, role, or classification an entity had specifically during the year 1945.
- 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_69a88a184cbc8190877791f6552c2484 |
completed | March 4, 2026, 7:38 p.m. |
| NER | Named-entity recognition | batch_69abbe8b9c0881908373eabc7f81c394 |
completed | March 7, 2026, 5:58 a.m. |
| PD | Predicate disambiguation | batch_69abbd9c90408190b6b65498ca43ce26 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:45 p.m.