Triple
T14587289
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Robinson-Patman Act |
E342349
|
entity |
| Predicate | allowsDefense |
P108546
|
FINISHED |
| Object | cost justification defense |
—
|
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 justification defense | Statement: [Robinson-Patman Act, allowsDefense, cost justification defense]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allowsDefense Context triple: [Robinson-Patman Act, allowsDefense, cost justification defense]
-
A.
canBeDefendedIn
Indicates that something (such as a claim, action, or position) is capable of being justified or supported within a specified context, forum, or framework.
-
B.
defends
Indicates that one entity protects or supports another entity against attack, criticism, or harm.
-
C.
recognizesDefense
Indicates that one entity acknowledges, identifies, or accepts another entity’s defensive action, strategy, or legal defense as such.
-
D.
defenseIncludes
chosen
Indicates that a defense strategy, plan, or system contains or incorporates a particular component, measure, or element as part of it.
-
E.
hasDefenseStrategy
Indicates that an entity employs or is associated with a particular plan or set of measures designed to protect against threats or attacks.
- 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_69d822ddc0f081909cd8163c7de298cd |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb421bb308190a457425429ef6aa5 |
completed | April 14, 2026, 9:39 p.m. |
| PD | Predicate disambiguation | batch_69de656a953481909a4645b004c40de7 |
completed | April 14, 2026, 4:03 p.m. |
Created at: April 10, 2026, 1:24 a.m.