Triple
T29118517
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Naval Defence Act 1910 |
E737111
|
entity |
| Predicate | replacesOrSupersedes |
P137696
|
FINISHED |
| Object | earlier colonial naval defence arrangements |
—
|
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: earlier colonial naval defence arrangements | Statement: [Naval Defence Act 1910, replacesOrSupersedes, earlier colonial naval defence arrangements]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: replacesOrSupersedes Context triple: [Naval Defence Act 1910, replacesOrSupersedes, earlier colonial naval defence arrangements]
-
A.
repealsOrSupersedes
chosen
Indicates that one legal act, rule, or provision invalidates, replaces, or takes precedence over another.
-
B.
wasSupersededBy
Indicates that one entity has been replaced or made obsolete by another entity that takes over its role or function.
-
C.
supersededByDate
Indicates the date on which something is replaced or rendered obsolete by a newer version or successor.
-
D.
oftenReplacedBy
Indicates that one entity is frequently substituted or superseded by another in similar contexts or uses.
-
E.
placedBy
Indicates that one entity was positioned, set, or put in a location or context by another entity.
- 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_69f077ed54e08190bb02a744e8121a66 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f78c61ed4c8190ad84c918fa9af55a |
completed | May 3, 2026, 5:56 p.m. |
| PD | Predicate disambiguation | batch_69f78b8cb3a881909ebaac1b503988c2 |
completed | May 3, 2026, 5:53 p.m. |
Created at: April 28, 2026, 11:24 a.m.