Triple
T29699746
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Naval Act of 1938 |
E751448
|
entity |
| Predicate | authorizedIncrease |
P116686
|
FINISHED |
| Object | 20 percent increase in U.S. Navy strength |
—
|
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: 20 percent increase in U.S. Navy strength | Statement: [Naval Act of 1938, authorizedIncrease, 20 percent increase in U.S. Navy strength]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: authorizedIncrease Context triple: [Naval Act of 1938, authorizedIncrease, 20 percent increase in U.S. Navy strength]
-
A.
wasTemporarilyIncreasedBy
Indicates that the value or level of something was raised for a limited period of time by a specified agent or cause.
-
B.
authorizedForceLevel
chosen
Indicates the level or extent of force that an entity is permitted or sanctioned to use in a given context.
-
C.
raisesLevelCapTo
Indicates that one entity increases the maximum allowable level of another entity to a specified value.
-
D.
subsequentIncrease
Indicates that one quantity or value increases after a prior event, state, or change has occurred.
-
E.
clearanceIncreasedBy
Indicates that the level or amount of clearance has been raised by a specified value or factor.
- 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_69f0d6266f8481909e70bb41cda18587 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69fba78aca4c8190b8f1831e8cc04e06 |
completed | May 6, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69fba34a65a4819088bac6c17542d71c |
completed | May 6, 2026, 8:23 p.m. |
Created at: April 28, 2026, 7:23 p.m.