Triple
T32400523
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | YOSEMITE |
E827934
|
entity |
| Predicate | controlComparator |
P156221
|
FINISHED |
| Object | aflibercept |
—
|
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: aflibercept | Statement: [YOSEMITE, controlComparator, aflibercept]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: controlComparator Context triple: [YOSEMITE, controlComparator, aflibercept]
-
A.
comparisonSystem
Indicates a relationship where one entity serves as the system, framework, or method used to compare or evaluate another entity.
-
B.
comparisonType
Indicates the specific kind of comparison being made between two or more values or entities (e.g., equality, inequality, ordering, or similarity).
-
C.
controlsWith
Indicates that one entity exercises authority, direction, or regulatory power over another entity through specific means or mechanisms.
-
D.
comparisonUnit
chosen
Indicates that one entity serves as the reference or baseline unit against which another entity is compared or measured.
-
E.
isComparedTo
Indicates that one entity is evaluated or measured in relation to another to highlight similarities, differences, or relative qualities.
- 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_69f34919342c8190a4c3bf35a90d4e58 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fe163a41a0819098403b470e327d29 |
completed | May 8, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69fe1358db5c819092570814a37ef5bd |
completed | May 8, 2026, 4:46 p.m. |
Created at: May 1, 2026, 12:52 a.m.