Triple
T3604265
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PRR K4s |
E76330
|
entity |
| Predicate | tenderType |
P49899
|
FINISHED |
| Object | coal and water tender |
—
|
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: coal and water tender | Statement: [PRR K4s, tenderType, coal and water tender]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tenderType Context triple: [PRR K4s, tenderType, coal and water tender]
-
A.
biddingProcessType
Indicates the specific method or procedure used to conduct a bidding or tendering process between parties.
-
B.
typeOfContract
Indicates the specific kind or category of contractual agreement that applies between the related entities.
-
C.
offeringType
Indicates the category or nature of what is being offered in a transaction or interaction (e.g., product, service, or other type of offering).
-
D.
typeOfNegotiation
Indicates the specific kind or category of negotiation process that characterizes the interaction between the involved parties.
-
E.
procurementMethod
Indicates the specific process or approach used to acquire goods, services, or works (e.g., open tender, direct purchase, negotiated procedure).
- 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_69ad85d93dcc819094fba90cf70f4996 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc1e07bc481908d9fce18d36d8e0d |
completed | March 8, 2026, 6:37 p.m. |
| PD | Predicate disambiguation | batch_69adb83d8b1c8190b3bddbc5dc995a87 |
completed | March 8, 2026, 5:56 p.m. |
| PDg | Predicate description generation | batch_69adb8e4ba948190a9b777cf7f788b96 |
completed | March 8, 2026, 5:59 p.m. |
Created at: March 8, 2026, 3:22 p.m.