Triple
T23635151
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Posse Comitatus Act |
E583722
|
entity |
| Predicate | influencedApplicationOf |
P9
|
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: [Posse Comitatus Act, influencedApplicationOf, United States Navy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: influencedApplicationOf Context triple: [Posse Comitatus Act, influencedApplicationOf, United States Navy]
-
A.
relatedApplication
Indicates that one application has a defined connection or association with another application, such as dependency, complementarity, or functional linkage.
-
B.
influencedTechnology
Indicates that one entity has had a causal or shaping impact on the development, design, or use of a technological entity.
-
C.
influenced
chosen
Indicates that one entity has affected, shaped, or altered another entity’s state, behavior, or characteristics.
-
D.
appliedAs
Indicates that one entity submitted itself or was put forward for consideration in a particular role, position, or context relative to another entity.
-
E.
appliedFrom
Indicates that an application or request was initiated starting at or originating from a particular source, location, or context.
- 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_69e248fe1c2c8190ac914d2442ff3d26 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b1eb38a481909f7ceeaefb7b43ce |
completed | April 29, 2026, 7:23 a.m. |
| PD | Predicate disambiguation | batch_69f118d7903c8190bb590a71771e93af |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:47 p.m.