Triple
T15419812
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States wartime aircraft production program |
E369343
|
entity |
| Predicate | usedPolicy |
P118714
|
FINISHED |
| Object | cost-plus contracts |
—
|
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: cost-plus contracts | Statement: [United States wartime aircraft production program, usedPolicy, cost-plus contracts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedPolicy Context triple: [United States wartime aircraft production program, usedPolicy, cost-plus contracts]
-
A.
usagePolicy
Indicates the rules or conditions governing how something may be used or accessed.
-
B.
usesPolicyRate
Indicates that one entity applies or bases its actions or decisions on a specified policy interest rate.
-
C.
establishedPolicy
Indicates that a policy has been formally created, adopted, and put into effect as a guiding rule or standard.
-
D.
endedPolicy
Indicates that a previously active policy has been brought to an end or terminated.
-
E.
usesPolicyModel
Indicates that one entity applies, relies on, or operates according to a particular policy model.
- F. None of above. chosen
Provenance (4 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_69d85a1849f48190bf898068b2806fae |
completed | April 10, 2026, 2:02 a.m. |
| NER | Named-entity recognition | batch_69e03ebce4f48190ba282ecb4fb2f6fa |
completed | April 16, 2026, 1:43 a.m. |
| PD | Predicate disambiguation | batch_69ded27f45548190a6d2b1b85cb47444 |
completed | April 14, 2026, 11:49 p.m. |
| PDg | Predicate description generation | batch_69ded57005608190886cd01f640dfedb |
completed | April 15, 2026, 12:01 a.m. |
Created at: April 10, 2026, 3:20 a.m.