Triple
T26492736
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Doppler ultrasound |
E669200
|
entity |
| Predicate | nonInvasive |
P129486
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Doppler ultrasound, nonInvasive, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nonInvasive Context triple: [Doppler ultrasound, nonInvasive, true]
-
A.
isNoninvasive
chosen
Indicates that an action, procedure, or method does not require entering the body or significantly disrupting the subject’s physical integrity.
-
B.
nonDestructive
Indicates that an action or process does not cause damage, loss, or permanent alteration to the entities involved.
-
C.
nonVolatile
Indicates that the associated entity or state does not change, disappear, or lose its value when power is removed or over time.
-
D.
nonperturbativeIn
Indicates that something occurs, is treated, or is valid in a nonperturbative regime or framework within a specified context or system.
-
E.
nonConstructive
Indicates that the relationship or action does not provide a direct, explicit method or example to realize or build the object, outcome, or proof it asserts exists.
- 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_69eeb319007081909642b414b114b35a |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f613535c1c81908e8da8d785be0cb4 |
completed | May 2, 2026, 3:08 p.m. |
| PD | Predicate disambiguation | batch_69f602d5c8808190a1fdbebd6f0981e8 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 27, 2026, 1:05 a.m.