Triple
T22271500
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NIT |
E550488
|
entity |
| Predicate | hasAutomaticBids |
P147644
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [NIT, hasAutomaticBids, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAutomaticBids Context triple: [NIT, hasAutomaticBids, yes]
-
A.
numberOfAutomaticBids
Indicates the total count of automatic bids associated with or placed in a given bidding context.
-
B.
grantsAutomaticBidTo
Indicates that one entity confers an automatic qualification or guaranteed entry (typically to a competition or event) upon another entity.
-
C.
automaticBidBasis
Indicates that one entity’s bid amount is determined automatically based on a specified rule, condition, or reference value relative to another entity.
-
D.
auctionMethod
Indicates the type or procedure of auction used to conduct a sale or bidding process between parties.
-
E.
notableBid
Indicates that an entity has made a bid or offer that is considered significant, prominent, or otherwise noteworthy in its context.
- 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_69e11e43d8208190aff4f9cf7f2c2a8a |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f141c056cc819088dae6f2b9a1d526 |
completed | April 28, 2026, 11:24 p.m. |
| PD | Predicate disambiguation | batch_69e72ff0363081909f794d19c8a64837 |
completed | April 21, 2026, 8:06 a.m. |
| PDg | Predicate description generation | batch_69e7342ce08c8190bc0a7085f4a952e7 |
completed | April 21, 2026, 8:24 a.m. |
Created at: April 16, 2026, 8:40 p.m.