Triple
T19338986
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. Navy Civilian Artist Corps |
E483698
|
entity |
| Predicate | hasCommissionType |
P39279
|
FINISHED |
| Object | civilian commission |
—
|
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: civilian commission | Statement: [U.S. Navy Civilian Artist Corps, hasCommissionType, civilian commission]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCommissionType Context triple: [U.S. Navy Civilian Artist Corps, hasCommissionType, civilian commission]
-
A.
commissionType
chosen
Indicates the specific kind or category of commission arrangement that applies to a given transaction or relationship.
-
B.
isCommissionSource
Indicates that one entity serves as the origin or basis from which another entity’s commission or referral fee is generated.
-
C.
hasCommitteeType
Indicates that an entity is associated with a committee of a specified type or classification.
-
D.
usesCommissionForm
Indicates that an entity conducts its commission-related activities through a specific standardized commission form.
-
E.
hasTypeOfCredit
Indicates that an entity is associated with or characterized by a specific type or category of credit.
- 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_69d8e8d244f8819080eb1f3491300db2 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e6185538d48190ae4fa3ac0b0ca182 |
completed | April 20, 2026, 12:13 p.m. |
| PD | Predicate disambiguation | batch_69e4dd12303c8190a2027c062b2dff40 |
completed | April 19, 2026, 1:48 p.m. |
Created at: April 10, 2026, 1:33 p.m.