Triple
T17130592
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Allied intelligence services |
E415711
|
entity |
| Predicate | hasPart |
P35
|
FINISHED |
| Object | SOE |
E148929
|
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: SOE | Statement: [Allied intelligence services, hasPart, SOE]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SOE Context triple: [Allied intelligence services, hasPart, SOE]
-
A.
SOE
chosen
SOE was a secret British World War II organization responsible for espionage, sabotage, and supporting resistance movements in enemy-occupied territories.
-
B.
SOE
SOE is the National Rail station code assigned to South Ealing station in London.
-
C.
Soe
Soe is a town in West Timor, Indonesia, known as an administrative and commercial center in the island’s interior highlands.
-
D.
SOF
SOF refers to Jordan’s elite Special Operations Forces, a highly trained military unit specializing in counterterrorism, unconventional warfare, and rapid-response missions.
-
E.
SOF
SOF is the three-letter IATA airport code for Sofia Airport, the main international airport serving Sofia, the capital of Bulgaria.
- 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_69d886d15af4819092f92f8a129763e6 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3f029d1a48190a9d4094827d11d23 |
completed | April 18, 2026, 8:57 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a01414cd5d481908d11eb230d2283cd |
completed | May 11, 2026, 2:39 a.m. |
Created at: April 10, 2026, 5:36 a.m.