Triple
T29699754
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Naval Act of 1938 |
E751448
|
entity |
| Predicate | expandedBranch |
P5633
|
FINISHED |
| Object | United States Navy |
—
|
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: United States Navy | Statement: [Naval Act of 1938, expandedBranch, United States Navy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: expandedBranch Context triple: [Naval Act of 1938, expandedBranch, United States Navy]
-
A.
expandedBy
chosen
Indicates that one entity increases, elaborates, or builds upon the scope, detail, or extent of another entity.
-
B.
expandedAs
Indicates that one entity is a more detailed, elaborated, or fully written-out form of another, capturing how the latter is expanded from the former.
-
C.
expandedElement
Indicates that one element has been unfolded, elaborated, or shown in greater detail relative to its more compact or summarized form.
-
D.
expandedAfter
Indicates that one entity increases in size, scope, or extent after another specified event or point in time.
-
E.
expandedComponent
Indicates that one entity is a more detailed or elaborated version (an expansion) of another component within a larger structure or system.
- 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_69f6afebd7ec8190ab696f363d84abf0 |
completed | May 3, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69f6aca204148190850a3dc325bc07b7 |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 28, 2026, 7:23 p.m.