Triple
T4066414
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IMS |
E86333
|
entity |
| Predicate | isLeadingIn |
P53286
|
FINISHED |
| Object | metabolic disease research |
—
|
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: metabolic disease research | Statement: [IMS, isLeadingIn, metabolic disease research]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLeadingIn Context triple: [IMS, isLeadingIn, metabolic disease research]
-
A.
hasLeader
Indicates that one entity serves as the leader or head of another entity.
-
B.
requiresLeadingLeagueIn
Indicates that one entity must be preceded or led by another specified entity within a particular league or hierarchical grouping.
-
C.
isStateLed
Indicates that an activity, initiative, or process is directed, controlled, or primarily governed by a state-level authority or government.
-
D.
winsLeader
Indicates that one entity achieves victory or leadership over another in a competitive or comparative context.
-
E.
hasAdvantage
Indicates that one entity possesses a benefit, edge, or favorable position over another in a given context.
- 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_69aed93c69208190a4efac0efe3cd69b |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefbf58d9c8190936e453b0d397cb0 |
completed | March 9, 2026, 4:57 p.m. |
| PD | Predicate disambiguation | batch_69aef9061d2481908307cafc9e9b32c0 |
completed | March 9, 2026, 4:44 p.m. |
| PDg | Predicate description generation | batch_69aefa5c52648190b001027f4dba75cb |
completed | March 9, 2026, 4:50 p.m. |
Created at: March 9, 2026, 3:38 p.m.