Triple
T35404673
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Central Contractor Registration |
E1023333
|
entity |
| Predicate | containedDataType |
P202799
|
FINISHED |
| Object | DUNS number |
—
|
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: DUNS number | Statement: [Central Contractor Registration, containedDataType, DUNS number]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containedDataType Context triple: [Central Contractor Registration, containedDataType, DUNS number]
-
A.
dataTypes
Indicates that one entity specifies or defines the kinds or formats of data that are valid or expected for another entity.
-
B.
dataDatatype
Indicates that a piece of data is associated with, or constrained to, a specific datatype.
-
C.
datumType
Indicates the specific kind or category of data that characterizes or classifies a datum.
-
D.
dataTypeContributed
Indicates that an entity has provided or supplied a particular type or category of data.
-
E.
primaryDataType
Indicates that one data type is the main or default type associated with a given entity or context, as opposed to any secondary or auxiliary data types.
- 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_69f76df43ca4819098711ca4370f1bb9 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a00bc079314819096271bba60bee52d |
completed | May 10, 2026, 5:10 p.m. |
| PD | Predicate disambiguation | batch_6a00bba5bd408190ace5db0c4a90dc6f |
completed | May 10, 2026, 5:08 p.m. |
| PDg | Predicate description generation | batch_6a00bc06bf3081908973b6c05797299f |
completed | May 10, 2026, 5:10 p.m. |
Created at: May 3, 2026, 4:03 p.m.