Triple
T28133894
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Forth defences |
E714143
|
entity |
| Predicate | operatorDuringWWI |
P197051
|
FINISHED |
| Object | Admiralty |
—
|
NE NERFINISHED |
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: Admiralty | Statement: [Forth defences, operatorDuringWWI, Admiralty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatorDuringWWI Context triple: [Forth defences, operatorDuringWWI, Admiralty]
-
A.
operatorDuringWorldWarII
Indicates that an entity operated or was active in its role during the period of World War II.
-
B.
roleInWorldWarI
Indicates the specific function, position, or involvement an entity had during World War I.
-
C.
legalStatusDuringWWI
Indicates the legal condition or classification an entity held specifically during World War I (e.g., enemy alien, neutral, ally, civilian, combatant).
-
D.
worldWarIIService
Indicates that an entity served in some capacity during World War II.
-
E.
positionOnWorldWarI
Indicates a person’s or group’s stance, opinion, or policy regarding World War I.
- F. None of above. chosen
Provenance (4 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_69efd6af156c81908f50c2cd7db0e1ef |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69fe766490c081908c49c8cc07d0ae9b |
completed | May 8, 2026, 11:48 p.m. |
| PD | Predicate disambiguation | batch_69fe75bb5f4481908572a5ffcbdc5154 |
completed | May 8, 2026, 11:46 p.m. |
| PDg | Predicate description generation | batch_69fe7663b5bc81909524c40d3a172512 |
completed | May 8, 2026, 11:48 p.m. |
Created at: April 27, 2026, 9:48 p.m.