Triple
T18510656
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Instrument of Government of 1653 |
E452333
|
entity |
| Predicate | requiredNavySize |
P131953
|
FINISHED |
| Object | a fleet of ships (fixed establishment) |
—
|
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: a fleet of ships (fixed establishment) | Statement: [Instrument of Government of 1653, requiredNavySize, a fleet of ships (fixed establishment)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiredNavySize Context triple: [Instrument of Government of 1653, requiredNavySize, a fleet of ships (fixed establishment)]
-
A.
desiredSizeIndicates
Indicates that one entity specifies or reflects the preferred or intended size of another entity.
-
B.
crewRequired
Indicates that a certain number or type of crew members is necessary to operate or support the associated entity or activity.
-
C.
militarySize
Indicates the total number of personnel in a military force, typically including active-duty members and sometimes reserves.
-
D.
shipLength
Indicates the physical length measurement of a ship.
-
E.
numberOfSails
Indicates the quantity of sails associated with an entity, such as a boat or ship.
- 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_69d8d386df84819092355ebb260d848e |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e533457e608190988304bf8bc2db1c |
completed | April 19, 2026, 7:55 p.m. |
| PD | Predicate disambiguation | batch_69e469dbf5208190b6fc49e02a087f54 |
completed | April 19, 2026, 5:36 a.m. |
| PDg | Predicate description generation | batch_69e46d2b93bc8190a6070018d7046547 |
completed | April 19, 2026, 5:50 a.m. |
Created at: April 10, 2026, 11:36 a.m.