Triple
T26520826
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States clinical reference laboratory network |
E669944
|
entity |
| Predicate | testingComplexityLevel |
P61901
|
FINISHED |
| Object | high complexity |
—
|
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: high complexity | Statement: [United States clinical reference laboratory network, testingComplexityLevel, high complexity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: testingComplexityLevel Context triple: [United States clinical reference laboratory network, testingComplexityLevel, high complexity]
-
A.
hasComplexity
Indicates that something possesses a certain level or type of complexity, often in terms of structure, behavior, or difficulty.
-
B.
testComplexityCategories
chosen
Indicates the classification of tests according to their level or type of complexity.
-
C.
controlsComplexityBy
Indicates that one entity manages, limits, or regulates the complexity of another entity, process, or system.
-
D.
testingLevel
Indicates the degree or intensity to which something is examined, evaluated, or tested.
-
E.
hasReasoningComplexity
Indicates that an action, process, or decision involves a certain level or type of cognitive or logical complexity in its reasoning.
- 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_69eeb31b6dcc8190b30632dc3928a0c0 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f613c22a48819099858ab078b5562f |
completed | May 2, 2026, 3:09 p.m. |
| PD | Predicate disambiguation | batch_69f60b89cc048190a9feb24466006be0 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 27, 2026, 1:27 a.m.