Triple
T17288943
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Swiss Criminal Procedure Code |
E419731
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | StPO |
E511452
|
NE 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: StPO | Statement: [Swiss Criminal Procedure Code, abbreviation, StPO]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: StPO Context triple: [Swiss Criminal Procedure Code, abbreviation, StPO]
-
A.
StPO
chosen
StPO is the abbreviation for the German Code of Criminal Procedure, which governs how criminal investigations, prosecutions, and trials are conducted in Germany.
-
B.
SPO
SPO is the standard abbreviation used for the Spokane Chiefs, a major junior ice hockey team in the Western Hockey League.
-
C.
SPO
SPO is the standard abbreviation used for the Spokane Indians, a Minor League Baseball team based in Spokane, Washington.
-
D.
SCPO
SCPO is the commonly used abbreviation for a Senior Chief Petty Officer, a senior enlisted rank in the U.S. Navy.
-
E.
SPZO
SPZO is the ICAO airport code for Alejandro Velasco Astete International Airport, the main air gateway serving Cusco, Peru.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d886db32608190a61e18862c5a8af6 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e43781b7808190a0528ee9c54a0c66 |
completed | April 19, 2026, 2:01 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a017957c738819087341bcd51b55114 |
completed | May 11, 2026, 6:38 a.m. |
Created at: April 10, 2026, 5:40 a.m.