Triple
T5689124
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ARIA-H |
E125385
|
entity |
| Predicate | hasTypicalSequence |
P65957
|
FINISHED |
| Object | T2*-weighted MRI |
—
|
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: T2*-weighted MRI | Statement: [ARIA-H, hasTypicalSequence, T2*-weighted MRI]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypicalSequence Context triple: [ARIA-H, hasTypicalSequence, T2*-weighted MRI]
-
A.
hasTypicalSegmentNumber
Indicates that an entity is characterized by a usual or standard number of segments it possesses.
-
B.
hasTypicalCharacterType
Indicates that an entity is commonly associated with or exemplified by a particular type of character or persona.
-
C.
hasTypicalSubject
Indicates that something is commonly or characteristically used as the subject (agent or topic) of a given relation or action.
-
D.
isSubsequenceOf
Indicates that one sequence can be derived from another by deleting zero or more elements without changing the order of the remaining elements.
-
E.
hasSubsequent
Indicates that one entity occurs, appears, or is positioned after another in a defined sequence or order.
- 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_69c0082bb19c8190823a4facd3cba79b |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c029014588819094a2a0f6f9b66bab |
completed | March 22, 2026, 5:38 p.m. |
| PD | Predicate disambiguation | batch_69c021c0e0408190ab6c3cd3f907e80f |
completed | March 22, 2026, 5:07 p.m. |
| PDg | Predicate description generation | batch_69c028fec2bc819083f5dca6a8d9d435 |
completed | March 22, 2026, 5:38 p.m. |
Created at: March 22, 2026, 3:44 p.m.