Triple
T140993
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Singapore |
E2848
|
entity |
| Predicate | surrenderingForce |
P4666
|
FINISHED |
| Object | British forces in Singapore |
—
|
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: British forces in Singapore | Statement: [Battle of Singapore, surrenderingForce, British forces in Singapore]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: surrenderingForce Context triple: [Battle of Singapore, surrenderingForce, British forces in Singapore]
-
A.
surrenderingParty
chosen
Indicates the party that yields control, rights, or possession to another in a surrender or transfer arrangement.
-
B.
countrySurrendering
Indicates that one country formally yields to another country’s authority or control, typically ending a conflict or war.
-
C.
opposingForce
Indicates a relationship where one entity actively resists, counters, or works against the actions, goals, or influence of another entity.
-
D.
primaryUSForces
Indicates that the referenced forces constitute the main or principal contingent of United States military forces in a given context or operation.
-
E.
surrenderEvent
Indicates an event in which one party yields or gives up control, rights, or resistance to another party.
- 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_69a2521e35c08190b28e5c9f1e3c9b59 |
completed | Feb. 28, 2026, 2:25 a.m. |
| NER | Named-entity recognition | batch_69a2580ca15481909fa3e87d804a1b23 |
completed | Feb. 28, 2026, 2:50 a.m. |
| PD | Predicate disambiguation | batch_69a2565559ac81909e0c4e095a7dfa27 |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:31 a.m.