Triple
T19773062
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ibrance |
E474934
|
entity |
| Predicate | hasAdministrationCycle |
P71429
|
FINISHED |
| Object | 28-day cycle |
—
|
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: 28-day cycle | Statement: [Ibrance, hasAdministrationCycle, 28-day cycle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAdministrationCycle Context triple: [Ibrance, hasAdministrationCycle, 28-day cycle]
-
A.
hasElectionAdministration
Indicates that one entity is responsible for organizing, managing, or overseeing the election processes of another entity.
-
B.
hasActivityCycle
chosen
Indicates that an entity exhibits a recurring pattern or cycle of activity over time.
-
C.
hasAdministrationSchedule
Indicates that there is a defined plan or timetable specifying when and how an entity is to be administered or given.
-
D.
hasRedistrictingCycle
Indicates that an entity is associated with a specific schedule or sequence of redistricting events, such as when and how its electoral districts are periodically redrawn.
-
E.
evaluationCycle
Indicates the recurring period or sequence in which evaluations or assessments are conducted and reviewed.
- 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_69d8e51a43a08190956bc6df13c91a77 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6535e450c8190a2628245ae0d0bd3 |
completed | April 20, 2026, 4:25 p.m. |
| PD | Predicate disambiguation | batch_69e53053ed2881908400becdfada7fd3 |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 1:48 p.m.