Triple
T2190611
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Remicade |
E49851
|
entity |
| Predicate | hasMaintenanceInterval |
P7407
|
FINISHED |
| Object | every 6 to 8 weeks |
—
|
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: every 6 to 8 weeks | Statement: [Remicade, hasMaintenanceInterval, every 6 to 8 weeks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMaintenanceInterval Context triple: [Remicade, hasMaintenanceInterval, every 6 to 8 weeks]
-
A.
hasMaintenanceBase
Indicates that an entity is supported, serviced, or maintained at a specific base or maintenance facility.
-
B.
maintainedWithin
Indicates that one entity is kept, preserved, or sustained inside the boundaries or context of another entity.
-
C.
tienePeriodicidad
chosen
Indicates that something occurs, recurs, or is scheduled with a specific regular frequency or periodic pattern.
-
D.
hasMaintenancePort
Indicates that an entity is equipped with a dedicated port or interface used specifically for maintenance, diagnostics, or service operations.
-
E.
hasCountingPeriod
Indicates that there is a defined time span or interval over which occurrences, quantities, or measurements related to an entity are counted or aggregated.
- 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_69a88aaba3c48190b351cab9b26989ff |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abbf9e99f08190892d34485c8f2f25 |
completed | March 7, 2026, 6:03 a.m. |
| PD | Predicate disambiguation | batch_69abbda32d1881909d1fd83a751fb21c |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:46 p.m.