Triple
T2138567
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lucentis |
E46708
|
entity |
| Predicate | hasAdministrationPattern |
P11436
|
FINISHED |
| Object | treat-and-extend regimens may be used |
—
|
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: treat-and-extend regimens may be used | Statement: [Lucentis, hasAdministrationPattern, treat-and-extend regimens may be used]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAdministrationPattern Context triple: [Lucentis, hasAdministrationPattern, treat-and-extend regimens may be used]
-
A.
hasAdministrativeType
Indicates that an entity is associated with a specific category or level of administrative classification (such as type of jurisdiction or administrative unit).
-
B.
hasAdministrationSite
Indicates the specific location or site on or in a subject where a substance, treatment, or intervention is administered.
-
C.
hasManagement
Indicates that one entity exercises managerial authority or oversight over another entity.
-
D.
hasAdministrativeArea
Indicates that one entity serves as the governing or jurisdictional area responsible for administering another entity.
-
E.
typeOfAdministration
chosen
Indicates the specific form or system of administration applied to or governing an entity.
- 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_69a88a174ab48190a5db20c132e5dccf |
completed | March 4, 2026, 7:37 p.m. |
| NER | Named-entity recognition | batch_69abbf74147c81908793c3694894f94a |
completed | March 7, 2026, 6:02 a.m. |
| PD | Predicate disambiguation | batch_69abbd96a3b0819081efbfef975e1513 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:44 p.m.