Triple
T31413983
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Technology and Construction Court |
E801341
|
entity |
| Predicate | typicalCaseValue |
—
|
GENERATED |
| Object | high-value disputes |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalCaseValue Context triple: [Technology and Construction Court, typicalCaseValue, high-value disputes]
-
A.
typicalValueFor
chosen
Indicates that one entity represents a standard, representative, or commonly occurring value associated with another entity.
-
B.
typicalCaseTypes
Indicates the kinds or categories of cases that are most commonly associated with or handled by a given entity.
-
C.
typicalKey
Indicates that the referenced key is the standard or most commonly used key associated with an entity or context.
-
D.
typicalOption
Indicates that one option is considered standard, common, or most representative among a set of possible options.
-
E.
typicalProperty
Indicates that a certain property is characteristically or commonly associated with an entity, reflecting what is typical for that entity.
- F. None of above.
Provenance (1 batch)
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_69f348c0dd648190bf2fd7642f78eb06 |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 8:41 p.m.