Triple
T7090190
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hunt Construction Group |
E165170
|
entity |
| Predicate | typicalContractForm |
P405
|
FINISHED |
| Object | construction management at-risk |
—
|
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: construction management at-risk | Statement: [Hunt Construction Group, typicalContractForm, construction management at-risk]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalContractForm Context triple: [Hunt Construction Group, typicalContractForm, construction management at-risk]
-
A.
typicalForm
Indicates that one entity represents the standard, characteristic, or most common form or shape in which another entity typically appears or is realized.
-
B.
typeOfContract
chosen
Indicates the specific kind or category of contractual agreement that applies between the related entities.
-
C.
typicalLegalForm
Indicates the standard or commonly used legal organizational form associated with an entity.
-
D.
contractValue
Indicates the monetary worth or agreed-upon financial amount specified in a contract between parties.
-
E.
contractFeature
Indicates that one entity is a feature, term, or provision that is included in or associated with a particular contract.
- 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_69c6887d98408190912b9580666b0c1d |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e53012b081908bf40541d85c82f1 |
completed | March 27, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69c6e1c172148190bf290c07bf579d1f |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:41 p.m.