Triple
T35380193
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SDOs |
E1022621
|
entity |
| Predicate | usesOutputIn |
P64275
|
FINISHED |
| Object | procurement specifications |
—
|
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: procurement specifications | Statement: [SDOs, usesOutputIn, procurement specifications]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesOutputIn Context triple: [SDOs, usesOutputIn, procurement specifications]
-
A.
outputUsedBy
chosen
Indicates that a particular output produced by one entity is consumed, referenced, or otherwise utilized by another entity.
-
B.
outputIs
Indicates that one entity functions as the result, product, or outcome produced by another entity or process.
-
C.
usesDataIn
Indicates that one entity relies on, accesses, or incorporates data from another entity in performing its function or operation.
-
D.
usedOutside
Indicates that something is utilized or applied in a context, location, or situation external to its primary or original setting.
-
E.
usedVia
Indicates that an entity performs or achieves something by means of, or through the use of, another entity or mechanism.
- 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_69f76df28d8c819089f2c5799fe7d079 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f79533b88c8190934ec4cb21770e24 |
completed | May 3, 2026, 6:34 p.m. |
| PD | Predicate disambiguation | batch_69f79104f5b48190a496cdffde8472da |
completed | May 3, 2026, 6:16 p.m. |
Created at: May 3, 2026, 4:03 p.m.