Triple
T9458461
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Technology and Construction Court |
E228077
|
entity |
| Predicate | typicalClaimValue |
P89058
|
FINISHED |
| Object | high value |
—
|
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: high value | Statement: [Technology and Construction Court, typicalClaimValue, high value]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalClaimValue Context triple: [Technology and Construction Court, typicalClaimValue, high value]
-
A.
typeOfClaim
Indicates the specific category or nature of a claim being made in relation to an entity or statement.
-
B.
typicalClaimsTested
Indicates that the usual or standard claims associated with something have been examined or verified through testing.
-
C.
typicalAwardAmount
Indicates the usual or most common amount of an award given in this relationship.
-
D.
typicalMeasure
Indicates the standard or characteristic quantitative measure typically associated with something, such as its usual size, weight, duration, or other magnitude.
-
E.
mainClaim
Indicates that one statement is presented as the central or primary assertion being made about a topic.
- 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_69ca843b123881909b0e60028475d12d |
completed | March 30, 2026, 2:10 p.m. |
| NER | Named-entity recognition | batch_69cd7f924f3081909dd937cbe6802881 |
completed | April 1, 2026, 8:26 p.m. |
| PD | Predicate disambiguation | batch_69cca55caaa8819089c5138e014892d3 |
completed | April 1, 2026, 4:55 a.m. |
| PDg | Predicate description generation | batch_69ccbf9b080c819098934a18cf2bac5d |
completed | April 1, 2026, 6:47 a.m. |
Created at: March 30, 2026, 7:52 p.m.