Triple
T14787359
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coast Guard Act, 1978 |
E347562
|
entity |
| Predicate | definesStatus |
P101079
|
FINISHED |
| Object | armed force of the Union |
—
|
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: armed force of the Union | Statement: [Coast Guard Act, 1978, definesStatus, armed force of the Union]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesStatus Context triple: [Coast Guard Act, 1978, definesStatus, armed force of the Union]
-
A.
definedStatusFor
chosen
Indicates that one entity establishes or specifies the status or state assigned to another entity.
-
B.
recognizesStatus
Indicates that one entity acknowledges or accepts the official status or standing of another entity.
-
C.
designationStatus
Indicates the current official classification or standing assigned to an entity within a defined system or process.
-
D.
canonicalStatus
Indicates the formal or official standing of an entity within an established authoritative or normative system.
-
E.
governsStatusOf
Indicates that one entity has authority or control over determining or regulating the status or condition of 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_69d822e9b9e08190bedcc31a163fda82 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69decaa083e481908336d58d026eec32 |
completed | April 14, 2026, 11:15 p.m. |
| PD | Predicate disambiguation | batch_69de8c090d1081909b5a9bf437499d6c |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:31 a.m.