Triple
T12130907
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | D.N.H. |
E288931
|
entity |
| Predicate | emblematicSystem |
P72227
|
FINISHED |
| Object | United States adversarial legal system |
—
|
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: United States adversarial legal system | Statement: [D.N.H., emblematicSystem, United States adversarial legal system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: emblematicSystem Context triple: [D.N.H., emblematicSystem, United States adversarial legal system]
-
A.
emblematicModel
Indicates that one entity serves as a representative or symbolic example of another entity, capturing its defining characteristics or ideals.
-
B.
emblematicFor
chosen
Indicates that something serves as a representative symbol or characteristic example of something else.
-
C.
emblematicPractice
Indicates a practice or behavior that symbolically represents, expresses, or typifies a group, identity, or concept.
-
D.
emblemName
Indicates that a specified name is the official or recognized title of an emblem.
-
E.
emblematicField
Indicates that a particular field or attribute serves as a symbolic or representative marker for an entity or concept.
- 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_69d6ab4b5e4c81909950b17151eb0951 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d91841615c819097f20a7447a1b8f4 |
completed | April 10, 2026, 3:33 p.m. |
| PD | Predicate disambiguation | batch_69d91508f8008190b3a90ec0bf0953ca |
completed | April 10, 2026, 3:19 p.m. |
Created at: April 8, 2026, 9:49 p.m.