Triple
T15974324
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CT colonography |
E387404
|
entity |
| Predicate | isLessInvasiveThan |
P120688
|
FINISHED |
| Object | optical colonoscopy |
—
|
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: optical colonoscopy | Statement: [CT colonography, isLessInvasiveThan, optical colonoscopy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLessInvasiveThan Context triple: [CT colonography, isLessInvasiveThan, optical colonoscopy]
-
A.
wasPioneeredInSurgeryBy
Indicates that a particular surgical technique, procedure, or approach was first developed, introduced, or trailblazed by a specific surgeon or surgical team.
-
B.
operatedWith
Indicates that an entity performed an action, function, or process using a specified tool, method, or instrument.
-
C.
hasSurgery
Indicates that a surgical procedure is performed on or undergone by an entity.
-
D.
isLessTechnicalThan
Indicates that one entity possesses a lower level of technical complexity, expertise, or detail compared to another entity.
-
E.
operatedThrough
Indicates that an action, process, or influence is carried out or mediated via a particular intermediary, channel, or mechanism.
- 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_69d86da94ccc819083d187f5dc6a123e |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e173b3bf6c81909230170e833d7ce7 |
completed | April 16, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_69e142d6fb588190b4176eab4bbae774 |
completed | April 16, 2026, 8:13 p.m. |
| PDg | Predicate description generation | batch_69e173af801c8190bfc0f602831bb594 |
completed | April 16, 2026, 11:41 p.m. |
Created at: April 10, 2026, 4:54 a.m.